Day 2: Scope, Schedule, and Cost Management - Self Paced
Lesson 5: Scope Management
13 Topics
Lesson 6: Schedule Management
17 Topics
Lesson 7: Cost Management
9 Topics
Day 3: Quality, Resource, and Communications - Self Paced
Project Scope Statement
This space intentionally left blank.
- Let us look at the project scope statement. A lot of folks get confused between the project charter and the project scope statement so let’s learn about the project scope statement by looking at the differences between the two.
- The project charter shouldn’t be changed once it’s approved.
- The project scope statement can be iterated till there is agreement among the stakeholders but even after it’s baselined, changes can be addressed through the Integrated Change Control process.
- The charter contains the project justification, measurable project objectives and related success criteria, high-level requirements, high-level product specification, summary milestone schedule, summary budget, project approval requirements, assigned PM, responsibility/authority level of the PM, and name and responsibility of those authorizing the charter
- The scope statement contains the product scope description that’s been progressively elaborated, project deliverables, product user acceptance criteria, project boundaries, project constraints, and project assumptions.
- Let’s look at it another way
- With the project charter, you are looking at high level information while with the scope statement, you are looking at the detailed information.
- Also, with the charter, you are dealing with high level objectives gathered from the sponsor or customer while with the scope statement, you are looking at the translation of those objectives while working with the key stakeholders. The objectives are translated into detailed scope, deliverables, and what is and is not included in the project along with the assumptions and constraints you learned while working with the stakeholders and the project team.
This is the exam perspective.