Appearance
6.1 Scope Planning
Scope defines the boundaries of the mission. It is the "What" the team will build and, just as importantly, the "What Not."
🛠️ The Scope Toolbox
The way you define scope depends on the stability of your requirements.
Predictive Tools
- WBS (Work Breakdown Structure): Decomposing work into manageable "Work Packages."
- WBS Dictionary: Detailed specs for every WBS element.
- Project Scope Statement: Written description of deliverables and exclusions.
Agile Tools
- Product Backlog: A dynamic, prioritized list of User Stories.
- User Stories: "As a [role], I want [action], so that [value]."
- Definition of Done (DoD): The non-negotiable checklist for every story.
🏗️ The WBS: Foundation of Control
In the PMP world, the WBS is the 100% rule: If it isn't in the WBS, it isn't in the project.
- Work Packages: The lowest level of the WBS where cost and duration can be reliably estimated.
- Control Accounts: Management points where scope, budget, and actual cost are integrated.
- Requirements Traceability Matrix (RTM): A table that links requirements to their origin and the deliverables that satisfy them. (Crucial for 2026 Compliance!)
🚦 Scope Creep vs. Gold Plating
Two major risks every PM must fight:
- Scope Creep: The uncontrolled expansion of scope without adjustments to time or cost.
- Gold Plating: The team adding "extra" features that weren't requested. (Even if they are free, they are considered a waste of resources).
🛠️ 2026 Shift: Continuous Backlog Refinement
In modern practice, the Product Owner and Team perform Backlog Refinement (Grooming) continuously. They break down "Epics" into "User Stories" just-in-time for the next sprint, ensuring the team always works on the highest value items.
📝 Exam Insight: If an exam scenario says the team is "confused about what a specific task requires," the answer is usually to refer to the WBS Dictionary. If they are confused if a feature is "finished," refer to the Definition of Done.