HKSM
Accepted Deliverables
Project outputs—whether products, outcomes, or capabilities—that have been formally reviewed and approved by the customer or sponsors as meeting the agreed-upon acceptance criteria.
Key Points
- They result from a formal acceptance process confirming the deliverables meet predefined acceptance criteria.
- Acceptance follows verification; quality checks confirm correctness first, then the customer/sponsor approves.
- Documented acceptance often triggers payments, phase gates, or readiness for project or phase closure.
- Unaccepted deliverables typically lead to change requests, defect repairs, or rework until criteria are met.
Example
A software project completes a reporting module that passes internal testing (verified). The client conducts user acceptance testing against the agreed criteria and signs off. The signed-off module is recorded as an accepted deliverable.
PMP Example Question
After demonstrating a finished feature to the client, the client signs a document confirming the feature meets the agreed acceptance criteria. Which item should the project manager record?
- Verified deliverables
- Accepted deliverables
- Scope baseline
- Quality management plan
Correct Answer: B — Accepted deliverables
Explanation: Client sign-off confirming requirements were met produces accepted deliverables. Verification occurs before acceptance and does not imply customer approval.
