HKSM
Accepted Deliverables
Work products that satisfy the user story acceptance criteria and are formally approved by the Product Owner. Once approved, they are treated as accepted deliverables and may be released to customers at the Product Owner's discretion.
Key Points
- They must meet all defined user story acceptance criteria.
- The Product Owner provides the formal approval (acceptance) after review.
- Acceptance makes the deliverable eligible for release, but release timing is a business decision.
- Evidence of acceptance often includes passing tests, a successful demo, and documented sign-off or status change.
Example
In a sprint review, the team demonstrates the "one-click checkout" user story. All acceptance criteria (tax calculation, saved address selection, and confirmation page) are met. The Product Owner marks the story as accepted and moves it to "Ready for Release," to be included in the next deployment.
PMP Example Question
In an Agile project, what best describes an accepted deliverable?
- A feature the Scrum Master confirms meets the Definition of Done.
- Work the Product Owner approves because it meets the acceptance criteria, making it eligible for release.
- An increment deployed to staging with no critical defects.
- A user story completed with development and unit testing finished.
Correct Answer: B — Deliverables approved by the Product Owner after meeting acceptance criteria
Explanation: Acceptance is the Product Owner's decision based on the agreed acceptance criteria; completion, DoD, or deployment alone does not equal acceptance.
