CAPM Practice: Determine how to document project controls of predictive, plan-based projects

Scope validation (also called scope acceptance) is the process of getting formal customer or sponsor acceptance of completed deliverables. It involves inspection and review of deliverables against acceptance criteria and results in documented, formal acceptance. Scope validation differs from quality control (which verifies technical correctness) — it's about getting the customer to officially sign off.

**Why not A:** Verifying that scope was correctly decomposed in the WBS is part of the scope definition process, not scope validation. Scope validation occurs after deliverables are complete and focuses on customer acceptance, not on checking the WBS structure.

**Why not B:** Verifying that the scope management plan was followed is a quality assurance or process audit activity, not scope validation. Scope validation specifically focuses on obtaining formal customer acceptance of completed deliverables.

**Why not C:** Confirming that quality metrics are appropriate is part of quality planning. Scope validation is not concerned with metric selection — it focuses on whether completed deliverables meet the customer's requirements and acceptance criteria.