November 29, 2006
Defining Project Scope
Let’s face it, defining what project scope means is critical. We have all been in the meetings where two or three people leave with different impressions of the discussion. Creating a project scope statement is a key way to ensure everyone is on the same page. The Project Scope Statement defines the project scope and what needs to be accomplished to meet the project’s objectives.
The five inputs to defining project scope are:
- Organizational process assets – Organizational process assets provide information about standards that the company has already set in place—standards that are likely to be applied to every project. This information is re-used when creating the Project Scope Statement.
- Project Charter – The project charter authorizes the existence of the project. It outlines the project objectives, which project managers need to detail further in the Project Scope Statement.
- Preliminary Project Scope Statement – The Preliminary Project Scope Statement provides a description of the major project deliverables, project objectives, project assumptions, project constraints, and a statement of work.
- Project Scope Management Plan – The Project Scope Management Plan provides a description of how the stated project objectives will be developed within the detailed Project Scope Statement.
- Approved change requests – Change request which are agreed-upon and documented amendments to project scope. Approved change requests will ultimately be added to the Project Scope Statement.
There are several tools and techniques used to developing a detailed Project Scope Statement.
- Product analysis - Project managers use product analysis to improve their understanding of the project's product. Product analysis is important to scope planning because it helps project managers determine how the product is made.
- Alternatives identification - When creating a Project Scope Statement, project managers use alternatives identification to produce different ways of approaching project tasks. Lateral thinking and brainstorming are two examples of alternatives identification.
- Expert judgment - To make informed decisions, project managers use their own expert judgment and the expert judgment of others who have advanced skills or previous experience. These experts help project managers make decisions when developing the Project Scope Statement.
- Stakeholder analysis - Project managers use stakeholder analysis to identify the potential people, groups, and institutions that may affect or be affected by the project. After identifying the stakeholders, the importance of key people that may significantly influence the project's success is assessed.
After putting the effort in one earns to view the outputs, the outputs of the Scope Definition process are as follows:
- Detailed Project Scope Statement – The detailed project scope statement is the description of the project scope, major deliverables, project objectives, project assumptions, project constraints, and a statement of work. It provides a documented basis for making future project decisions.
- Requested changes - A requested change is a formally documented change request that is submitted for approval to the Integrated Change Control process.
- Project Scope Management Plan updates – Project scope management plan updates are contained within or is a part of the subsidiary plan of the Project Management Plan. It describes how the project scope will be defined, verified, and controlled, and how the Work Breakdown Structure (WBS) will be created and defined.
The detailed Project Scope Statement and the updated Project Scope Management Plan, as well as approved change requests, will be used as inputs for one of the most important items produced as part of the Planning Process Group—the Work Breakdown Structure.
Posted by Elyse at November 29, 2006 7:50 AM
Comments
Post a comment
Did you miss?
Decision Criteria Matrix
What do business analyst's do?
Implementing a project dashboard 101
Himss - Final Thoughts
HIMSS 2008 Perceptions - A first glance
Our best intentions and the effects of not collaborating
Quick Little Risk Management Checklist
Tasks, Projects, Programs
What do business analyst's do?
Implementing a project dashboard 101
Himss - Final Thoughts
HIMSS 2008 Perceptions - A first glance
Our best intentions and the effects of not collaborating
Quick Little Risk Management Checklist
Tasks, Projects, Programs
Archives
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
August 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
November 2005
October 2005
September 2005
August 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
Blogs
Cafe au Lait
Joel on Software
David Ross
Edward Prevost
Martin Fowler
The Health Care Blog
The Tales of Hoffman
The Business Word
Medical Rants
Christina's Considerations
Paul Levy
HIS Talk
Appropriate IT
Candid CIO
Joel on Software
David Ross
Edward Prevost
Martin Fowler
The Health Care Blog
The Tales of Hoffman
The Business Word
Medical Rants
Christina's Considerations
Paul Levy
HIS Talk
Appropriate IT
Candid CIO
Subscribe
© Copyright 2003 - 2007 Elyse Nielsen
RSS feed




