3.2 Scope Management and the WBS

Defining Scope Precisely

Scope management ensures the project includes all the work required — and only the work required — to finish successfully. The CAPM exam separates two scopes that students routinely confuse:

A useful test: if it describes the thing being built, it is product scope; if it describes the work to build it, it is project scope.

The Six Scope Processes

The requirements traceability matrix links each requirement to its origin and to the deliverable that satisfies it — a frequent exam answer for "how do you make sure no requirement is lost?"

The Work Breakdown Structure

The WBS is a deliverable-oriented hierarchical decomposition of the total scope. It is decomposed into nouns (deliverables), not verbs (actions). Decomposition stops at the work package, the lowest level — small enough to estimate cost and duration reliably and to assign to one owner.

Project (Level 1)
├── Deliverable 1 (Level 2)
│   ├── Sub-deliverable 1.1
│   │   ├── Work Package 1.1.1
│   │   └── Work Package 1.1.2
│   └── Sub-deliverable 1.2
├── Deliverable 2
└── Project Management work

Note the exam's hierarchy beyond the WBS: a work package is decomposed into activities, and activities are broken into milestones during schedule planning. Activities are NOT part of the WBS itself.

The 100% Rule

The 100% rule is the governing principle of WBS construction: the WBS must capture 100% of the work in the scope statement — internal, external, and project management work — and nothing more. The work at any child level must roll up to exactly 100% of its parent. If something is not in the WBS, it is not in the project; the WBS is therefore the primary defense against scope creep.

Two Scope Pathologies

Scope creep is managed by Control Scope plus formal change control; gold plating is prevented by clear documentation and team discipline. Both reduce, not increase, value.

Validate Scope vs. Control Quality

Exam tip: Control Quality runs FIRST (verify correctness), then Validate Scope (obtain formal acceptance). A verified deliverable goes into Validate Scope; an accepted deliverable comes out.

Collecting Requirements Well

Before scope can be defined, requirements must be collected. The CAPM exam expects familiarity with the elicitation techniques: interviews and focus groups for individual or small-group input, questionnaires and surveys for large dispersed audiences, brainstorming and nominal group technique for idea generation and ranking, prototyping for early tangible feedback, and benchmarking against other organizations.

Requirements are then captured in requirements documentation and tracked in the requirements traceability matrix, which links each requirement forward to a deliverable and backward to a business need so nothing is added or lost without notice. A frequent distractor: the matrix does not estimate cost or schedule; its job is traceability.

Decomposition and Rolling Wave Planning

Decomposition is the technique used to build the WBS — subdividing deliverables into smaller, more manageable components until reaching the work-package level. How far should you decompose? Far enough that you can reliably estimate cost and duration and assign clear accountability, but not so far that you create unmanageable administrative overhead. When later work is not yet clear, teams use rolling wave planning: near-term work is decomposed in detail now, while distant work stays at the planning-package level until more is known.

This is a form of progressive elaboration applied to scope and is fully compatible with predictive planning.

The Project Scope Statement

The project scope statement, an output of Define Scope, is more detailed than the charter and contains the product scope description, the project deliverables, acceptance criteria, and — critically for the exam — explicit exclusions (what is out of scope), along with constraints and assumptions. Documenting exclusions is a primary defense against scope creep, because it removes ambiguity about what the customer will and will not receive. Together with the WBS and WBS dictionary, the approved scope statement forms the scope baseline.

Common Exam Traps

• The WBS is decomposed into deliverables, not tasks; activities come later in schedule planning.
• Validate Scope is about acceptance by the customer; Control Quality is about internal correctness — and quality is checked first.
• The 100% rule means nothing exists outside the WBS, and child elements sum to exactly their parent.
• Scope creep is uncontrolled and stakeholder-driven; gold plating is deliberate and team-driven. Both destroy value and must be prevented.