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
Plan Scope Management — Document how scope will be defined, validated, and controlled
Collect Requirements — Gather stakeholder needs through interviews, surveys, workshops
Define Scope — Develop a detailed description of the project and product
Create WBS — Decompose deliverables into smaller, manageable components
Validate Scope — Formally accept completed deliverables with stakeholders
Control Scope — Monitor scope status and manage changes to the scope baseline
Requirements Collection
Techniques include:
Interviews — One-on-one discussions with stakeholders
Focus Groups — Moderated discussions with subject matter experts
Surveys/Questionnaires — Broad data collection from many stakeholders
Prototyping — Iterative mock-ups to refine requirements
Observation — Watching users in their work environment
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.
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.