Scope Management
Define it right or rebuild it twice
GanttGrind.com — Free PMP Study Guide
Overview
Scope Management is about defining exactly what the project will deliver — and equally important, what it will not. The scope baseline (project scope statement + WBS + WBS dictionary) becomes the reference point against which all deliverables are validated and all scope change requests are measured. A project with poorly defined scope is already in trouble before the first task begins.
The Work Breakdown Structure (WBS) is the most frequently tested artifact in this domain. The WBS decomposes the total project scope into hierarchical, manageable components — but those components represent deliverables, not activities. Activities come from the schedule management process. The lowest-level WBS components are called work packages, and each work package is documented in the WBS dictionary with scope of work, acceptance criteria, assumptions, and constraints.
Two concepts that constantly appear on the exam are scope creep and gold plating. Scope creep is uncontrolled expansion of project scope without authorization — it's bad. Gold plating is the team adding extra features or functionality beyond what was requested, believing it adds value — also bad, because it consumes budget and schedule without approval. Both represent scope control failures. When scope needs to change, the correct path is always a formal change request through integrated change control.
Must Know at a Glance
| Term / Concept | Definition |
|---|---|
| Product Scope | The features and functions that characterize a product or service. Measured against requirements. |
| Project Scope | The work performed to deliver the product/service/result with the specified features. Measured against the scope plan. |
| WBS (Work Breakdown Structure) | Hierarchical decomposition of total project scope into deliverables and work packages. Deliverable-oriented, not activity-oriented. |
| Work Package | The lowest-level WBS component; detailed enough to be estimated, scheduled, monitored, and controlled. |
| WBS Dictionary | Describes each WBS component: scope, deliverables, acceptance criteria, assumptions, responsible party. |
| Scope Baseline | Approved scope statement + WBS + WBS dictionary. Changes require formal change control. |
| Scope Creep | Uncontrolled expansion of scope without authorization, schedule, or cost adjustment. |
| Gold Plating | Adding features beyond what was requested without a change request. Always wrong on the exam. |
| Validate Scope | Monitoring & Controlling process. Formalizing acceptance of completed deliverables with the customer. |
| Control Scope | Monitoring & Controlling process. Managing changes to scope baseline; preventing scope creep. |
Process Sequence
These processes run in order — each one builds on the outputs of the previous.
- 1
Plan Scope Management
Creates the scope management plan defining how scope will be defined, validated, and controlled.
- 2
Collect Requirements
Documenting stakeholder needs, expectations, and conditions the project must meet.
- 3
Define Scope
Developing a detailed description of the project and product; producing the project scope statement.
- 4
Create WBS
Decomposing project deliverables and work into smaller, manageable components.
- 5
Validate Scope
Formalizing acceptance of completed project deliverables with customers and stakeholders.
- 6
Control Scope
Monitoring project and product scope; managing changes to the scope baseline.
Exam Strategy
How to approach these questions
The most tested distinction in scope management is Validate Scope vs. Control Quality. Validate Scope is about customer acceptance of completed deliverables (customer confirms it's what they asked for). Control Quality is about checking that deliverables meet quality standards (team confirms it was built correctly). Validate Scope involves the customer; Control Quality is internal. Both can happen in the same project cycle, and Control Quality usually happens before Validate Scope.
Common Mistakes
- ✕Confusing Validate Scope (customer acceptance) with Control Quality (internal quality checks).
- ✕Thinking the WBS contains activities — it contains deliverables and work packages, not activities.
- ✕Treating gold plating as helpful — it's a scope control failure that wastes budget and time.
- ✕Skipping the WBS dictionary — it's the document that makes the WBS actionable and auditable.
All 30 Topics in This Domain
Click any topic for the full explanation, key points, exam tips, and FAQs.
Project Scope
Project scope is the work that must be performed to deliver a product, service, or result with the specified features and functions.
Product Scope
Product scope is the features and functions that characterize a product, service, or result delivered by the project.
Plan Scope Management
Plan Scope Management is the process of creating a scope management plan that documents how project and product scope will be defined, validated, and controlled.
Scope Management Plan
The scope management plan is a component of the project management plan that describes how the project scope will be defined, developed, monitored, controlled, and validated.
Collect Requirements
Collect Requirements is the process of determining, documenting, and managing stakeholder needs and requirements to meet project objectives.
Requirements Documentation
Requirements documentation describes how individual requirements meet the business need for the project, capturing all requirements in enough detail for them to be measured and managed.
Requirements Traceability Matrix
A requirements traceability matrix (RTM) is a grid that links product requirements from their origin to the deliverables that satisfy them, ensuring each requirement adds business value and is tracked throughout the project.
Requirements Management Plan
The requirements management plan is a component of the project management plan that describes how requirements will be analyzed, documented, and managed throughout the project.
Define Scope
Define Scope is the process of developing a detailed description of the project and product, resulting in the project scope statement.
Project Scope Statement
The project scope statement is a detailed description of the project scope, major deliverables, assumptions, and constraints that provides a documented basis for making future project decisions.
Create WBS
Create WBS is the process of subdividing project deliverables and project work into smaller, more manageable components.
Work Breakdown Structure (WBS)
A work breakdown structure (WBS) is a hierarchical decomposition of the total scope of work to be carried out by the project team to accomplish the project objectives and create the required deliverables.
WBS Dictionary
The WBS dictionary is a document that provides detailed deliverable, activity, and scheduling information about each component in the work breakdown structure.
Work Package
A work package is the lowest level of the work breakdown structure, representing a deliverable or project work component that can be estimated, scheduled, monitored, and controlled.
Control Account
A control account is a management control point where scope, budget, actual cost, and schedule are integrated and compared to earned value for performance measurement.
Planning Package
A planning package is a WBS component below the control account with known work content but without detailed schedule activities, used as a placeholder for future planning.
Decomposition
Decomposition is a technique used to divide and subdivide the project scope and deliverables into smaller, more manageable parts until the work is defined at the work package level.
Validate Scope
Validate Scope is the process of formalizing acceptance of the completed project deliverables by the customer or sponsor.
Control Scope
Control Scope is the process of monitoring the status of the project and product scope and managing changes to the scope baseline.
Scope Baseline
The scope baseline is the approved version of the project scope statement, work breakdown structure (WBS), and its associated WBS dictionary, used as a reference for measuring project scope performance.
Scope Creep
Scope creep is the uncontrolled expansion of project scope without adjustments to time, cost, and resources, typically occurring when changes are made without going through integrated change control.
Gold Plating
Gold plating is the practice of adding extra features, functionality, or work to a deliverable beyond what was specified in the project scope, typically done by the project team without customer request or approval.
Accepted Deliverables
Accepted deliverables are completed deliverables that have been formally accepted by the customer or sponsor through the Validate Scope process, confirming they meet the defined acceptance criteria.
Verified Deliverables
Verified deliverables are completed project deliverables that have been checked and confirmed for correctness through the Control Quality process.
Product Analysis
Product analysis is a set of techniques used in the Define Scope process to translate product descriptions and objectives into tangible deliverables and requirements.
Alternatives Analysis
Alternatives analysis is a technique used to evaluate different approaches, methods, or options for accomplishing project work, helping the team select the best way to define and deliver the scope.
Product Backlog
The product backlog is an ordered list of everything that is known to be needed in the product, serving as the single source of requirements and the primary artifact for managing scope in agile projects.
User Stories
A user story is a short, simple description of a feature or requirement written from the perspective of the end user, following the format: "As a [role], I want [goal], so that [benefit]."
Story Points
Story points are a unit of measure used in agile to estimate the overall effort, complexity, and uncertainty involved in completing a user story or product backlog item.
Definition of Done
The definition of done (DoD) is a shared understanding within the agile team of the criteria that must be met before a product backlog item or increment is considered complete and ready for release.
Related Domains
Integration Management
Coordinating all project elements — charter, change control, lessons learned, and project closure.
Schedule Management
Planning and controlling the project timeline — critical path, dependencies, estimating, and compression.
Quality Management
Ensuring deliverables meet requirements — quality planning, assurance, control, and continuous improvement.
Test your knowledge
Practice scenario-based questions on this topic with detailed explanations.