CAPM · Question #70
curious about the difference between a verified deliverable and an accepted deliverable. Which of the following definitions can the project manager use to explain the difference?
The correct answer is C. An accepted deliverable meets acceptance criteria and is formally signed off and approved by the customer or sponsor; a verified deliverable is a completed project deliverable that has been checked and confirmed for accuracy through the Control Quality process.. A verified deliverable has passed Control Quality inspection for accuracy and completeness, while an accepted deliverable has additionally met customer acceptance criteria and received formal sign-off from the customer or sponsor.
Question
Options
- AAn accepted deliverable is approved by the project team; a verified deliverable is approved and formally signed off by the customer or sponsor.
- BAn accepted deliverable has been checked and confirmed for accuracy through the Control Quality process; a verified deliverable meets acceptance criteria that is formally signed off and approved by the customer or sponsor.
- CAn accepted deliverable meets acceptance criteria and is formally signed off and approved by the customer or sponsor; a verified deliverable is a completed project deliverable that has been checked and confirmed for accuracy through the Control Quality process.
- DAn accepted deliverable meets acceptance criteria and is signed off by the project manager; a verified deliverable meets acceptance criteria and is signed off by the customer or sponsor.
How the community answered
(35 responses)- A3% (1)
- B3% (1)
- C86% (30)
- D9% (3)
Why each option
A verified deliverable has passed Control Quality inspection for accuracy and completeness, while an accepted deliverable has additionally met customer acceptance criteria and received formal sign-off from the customer or sponsor.
This reverses the roles - accepted deliverables are approved by the customer or sponsor, not the project team, and verified deliverables are confirmed through quality control, not customer sign-off.
This reverses the definitions - a verified deliverable is the one confirmed through Control Quality, while an accepted deliverable is the one formally signed off by the customer or sponsor.
The PMBOK Guide draws a clear distinction: a verified deliverable is a completed output that has been checked and confirmed for correctness and completeness through the Control Quality process. An accepted deliverable goes further - it has been reviewed against formal acceptance criteria and formally approved and signed off by the customer or sponsor through the Validate Scope process. Verification (quality check) precedes and is a prerequisite for acceptance (stakeholder approval).
Acceptance requires customer or sponsor sign-off, not the project manager's signature; the project manager's approval alone does not constitute formal deliverable acceptance under PMBOK.
Concept tested: Verified vs accepted deliverable definitions in PMBOK
Source: https://www.pmi.org/pmbok-guide-standards/foundational/pmbok
Topics
Community Discussion
No community discussion yet for this question.