← Back to Tutorials

10. Scope Management

Cost & Scope

What is Scope Management?

Scope management ensures the project includes all the work required — and only the work required — to complete the project successfully. It prevents scope creep, where unauthorized changes expand the project beyond its original boundaries.

Scope Management Process

  1. Plan Scope Management — Document how scope will be defined, validated, and controlled
  2. Collect Requirements — Gather stakeholder needs through interviews, surveys, workshops
  3. Define Scope — Develop a detailed description of the project and product
  4. Create WBS — Decompose deliverables into smaller, manageable components
  5. Validate Scope — Formally accept completed deliverables with stakeholders
  6. Control Scope — Monitor scope status and manage changes to the scope baseline

Requirements Collection

Techniques include:

Work Breakdown Structure (WBS)

The WBS is a hierarchical decomposition of the total scope of work. Each descending level represents an increasingly detailed definition of the project work. The 100% Rule states that the WBS must capture all deliverables — nothing more, nothing less.

Website Launch Project
├── 1.0 Planning
│   ├── 1.1 Requirements
│   └── 1.2 Architecture
├── 2.0 Design
│   ├── 2.1 Wireframes
│   └── 2.2 Visual Design
├── 3.0 Development
│   ├── 3.1 Frontend
│   ├── 3.2 Backend
│   └── 3.3 Database
├── 4.0 Testing
└── 5.0 Deployment

Scope Creep

Scope creep occurs when features or requirements are added without proper review, impacting budget and schedule. Prevention strategies include a clear scope statement, a formal change control process, stakeholder education, and strict prioritization.

Verification & Control

Scope verification is the formal acceptance of completed deliverables. Scope control monitors the status of scope and manages changes to the scope baseline, using variance analysis to detect deviations.

Practice Task: Write a scope statement for a mobile app project. Include project objectives, deliverables, constraints, assumptions, and exclusions (out of scope). Create a WBS with at least 15 work packages decomposed to at least 3 levels. Describe a scenario of scope creep and how the change control process would handle it.