Project Scope Statement: The Baseline for Evaluating Change Requests
PMBOK v8 Definition
The project scope statement is the description of the project scope, major deliverables, assumptions, and constraints. It documents the entire scope, including the project and product scope. The statement describes the project’s deliverables in detail and provides a common understanding of the project scope among project stakeholders. It may contain explicit scope exclusions that assist in managing stakeholder expectations.
This document is an output of the Define Scope process (Planning Process Group, Scope Management Knowledge Area).
Why It Matters for the Exam
The project scope statement appears frequently on the PMI exam because it is the central document for scope management, change control, and stakeholder expectation management. Questions test your ability to distinguish it from the project charter, recognize its role as a baseline for evaluating change requests, and identify which components (exclusions, acceptance criteria, deliverables) belong exclusively to this document.
Key Points to Remember (for the exam)
- Main Output: Project scope statement (output of Define Scope process)
- Primary Purpose: Provides the baseline for evaluating whether requests for changes or additional work are contained within or outside the project’s boundaries
- Key Components:
- Project scope description (progressively elaborates product characteristics from charter)
- Deliverables
- Acceptance criteria
- Project exclusions (explicitly states what is out of scope)
- Critical Distinction from Charter: Project charter contains high-level information; project scope statement contains detailed description of scope components
- Role in Execution: Guides the project team’s work during execution and enables more detailed planning
- Scope Creep Prevention: Explicit exclusions help reduce scope creep and manage stakeholder expectations
- Progressive Elaboration: Scope components are progressively elaborated throughout the project
Typical PMI Exam Example
A project manager receives a change request to add a feature that was not included in the original scope. The project manager reviews the project scope statement and finds that the requested feature is listed under "project exclusions." What should the project manager do?
Answer: The change request falls outside the project's boundaries. The project manager should follow the formal change control process to evaluate the impact, but the scope statement provides clear evidence that this work was explicitly excluded.
PMI Exam Traps
-
Trap: Confusing the project scope statement with the project charter Reality: The charter contains high-level information; the scope statement contains detailed descriptions of deliverables, exclusions, and acceptance criteria
-
Trap: Thinking scope exclusions are optional or informal Reality: Project exclusions are explicitly stated in the project scope statement and are a formal tool to reduce scope creep
-
Trap: Believing the scope statement is created once and never updated Reality: Scope components are progressively elaborated throughout the project
-
Trap: Assuming the scope statement only describes what IS included Reality: It also documents what is excluded (project exclusions) to manage stakeholder expectations
Important PMI Connections
| Related Concept | Relationship Type | Exam Attention Point |
|---|---|---|
| Project Charter | Input / Higher-level predecessor | Charter has high-level info; scope statement has detailed components |
| Work Breakdown Structure (WBS) | Complementary output | WBS decomposes scope statement deliverables into work packages |
| Requirements Documentation | Input to Define Scope | Requirements are progressively elaborated into the scope description |
| Change Control Process | Uses scope statement as baseline | Scope statement determines if a change is inside or outside boundaries |
Quick Review Questions
-
What are the three main components of the project scope statement that are specifically listed in PMBOK v8?
-
How does the project scope statement differ from the project charter in terms of level of detail?
-
Why are project exclusions explicitly stated in the project scope statement?
-
What is the primary role of the project scope statement during project execution?
-
During which process is the project scope statement created, and in which Knowledge Area does that process belong?
PMBOK v8 Reference
Section 2.2.2.3 – Define Scope (Planning Process Group, Scope Management Knowledge Area)
Note: The project scope statement is also referenced in Section 2.2.2.4 (Develop Scope Structure) as the basis for creating the WBS, and in Section 4.3 (Change Control) as the baseline for evaluating change requests.