Scope Management and the WBS

Scope management ensures that the project includes all the work required — and only the work required — to complete the project successfully. Understanding scope management processes and the Work Breakdown Structure (WBS) is critical for the CAPM exam.

Product Scope vs. Project Scope

Scope Management Processes

---

The Work Breakdown Structure (WBS)

The WBS is a hierarchical decomposition of the total scope of work to be carried out by the project team. It organizes and defines the total scope of the project.

WBS Structure

Project (Level 1)
├── Deliverable 1 (Level 2)
│   ├── Sub-deliverable 1.1 (Level 3)
│   │   ├── Work Package 1.1.1 (Level 4)
│   │   └── Work Package 1.1.2
│   └── Sub-deliverable 1.2
│       ├── Work Package 1.2.1
│       └── Work Package 1.2.2
├── Deliverable 2
│   ├── Work Package 2.1
│   └── Work Package 2.2
└── Project Management (often included)
    ├── Planning activities
    └── Closing activities

Key WBS Terminology

---

The 100% Rule

The 100% rule states that the WBS must include 100% of the work defined by the project scope and capture all deliverables — both internal and external — including project management. This means:

• Every work package must roll up to its parent
• No work exists outside the WBS
• The sum of work at any level must equal 100% of the work at the level above

---

Scope Creep vs. Gold Plating

Both are negative and should be avoided:

• Scope creep is managed through the Control Scope process and formal change control
• Gold plating is prevented through clear scope documentation and team discipline

---

Validate Scope vs. Control Quality

Exam Tip: Control Quality typically happens BEFORE Validate Scope. You verify the work is correct (quality), then get formal acceptance (scope validation).