Project Management: Foundations to Practice · Scope Management and Work Breakdown Structures
Scope Verification and Control
Verification and control are two related but distinct disciplines: one confirms what has already been delivered, the other governs what happens when someone wants to change the plan.
Scope verification is the formal process of confirming that completed deliverables meet the acceptance criteria defined during scope planning, typically involving a review by the sponsor or customer before a deliverable is considered done [1]. This step exists specifically to catch the gap between 'technically matches the written specification' and 'actually satisfies what the stakeholder needed,' a gap that can be substantial even when the written specification itself seemed clear at the time.
- Scope verification confirms completed deliverables meet acceptance criteria through a formal sponsor or customer review.
- Scope control governs changes to scope through a formal process, preventing informal, undocumented scope drift.
- Excellent scope control cannot substitute for verification; a well-controlled change still needs to be checked against acceptance criteria once delivered.
- Skipping formal verification lets a technically-compliant but stakeholder-unsatisfying deliverable go undetected until it is expensive to fix.