CAPM · Question #247
What is the difference between verified and accepted deliverables?
The correct answer is C. Accepted deliverables have been formally signed off and approved by the authorized stakeholder; verified deliverables have been completed and checked for correctness. These two terms have distinct meanings in the PMBOK framework. Verified deliverables are the output of the Control Quality process - they have been completed and checked for correctness against quality standards by the project team. Accepted deliverables are the output of the…
Question
Options
- AAccepted deliverables have been completed and checked for correctness; verified deliverables have been formally approved by the customer or authorized stakeholder.
- BAccepted deliverables have been inspected by the quality team; verified deliverables are outputs from the Validate Scope process.
- CAccepted deliverables have been formally signed off and approved by the authorized stakeholder; verified deliverables have been completed and checked for correctness.
- DAccepted deliverables have been formally accepted by the project manager; verified deliverables are the outputs from the Control Quality process
How the community answered
(27 responses)- A4% (1)
- B7% (2)
- C85% (23)
- D4% (1)
Explanation
These two terms have distinct meanings in the PMBOK framework. Verified deliverables are the output of the Control Quality process - they have been completed and checked for correctness against quality standards by the project team. Accepted deliverables are the output of the Validate Scope process - they have been formally reviewed and signed off by the customer or authorized stakeholder. The flow is: produce → verify (internal QC) → validate (customer approval) → accept. Options A and D have the definitions reversed. Option B incorrectly attributes verified deliverables to the Validate Scope process.
Topics
Community Discussion
No community discussion yet for this question.