Validate Scope
Securing official sign-off from the customer or sponsor that completed deliverables meet the agreed requirements and acceptance criteria.
Key Points
- Confirms deliverables are complete and acceptable to stakeholders, not just technically correct.
- Uses verified deliverables, requirements, and acceptance criteria as inputs; outputs include accepted deliverables and possible change requests.
- Typically performed at the end of phases, iterations, or major milestones.
- Different from Control Quality (checks correctness) and Control Scope (manages scope changes).
Example
After QA verifies a report is error-free, the sponsor reviews it against the requirements and acceptance criteria. The sponsor signs an acceptance form for the report and requests changes to a dashboard that does not meet a stated requirement. This activity is Validate Scope.
PMP Example Question
During a phase gate, the sponsor signs off on three deliverables and rejects one because it fails to meet a documented acceptance criterion. Which process is being performed?
- Control Quality
- Validate Scope
- Control Scope
- Close Project or Phase
Correct Answer: B — Validate Scope (formal acceptance of completed deliverables)
Explanation: Validate Scope obtains stakeholder acceptance of completed deliverables; Control Quality checks correctness, Control Scope manages changes, and Close Project or Phase finalizes all activities.
