HKSM
Rejected Deliverables
Work outputs that do not satisfy the agreed acceptance criteria. The team maintains a running list of these items and updates it after each Sprint Review with any work the Product Owner did not accept.
Key Points
- Rejected deliverables failed one or more acceptance criteria and are not considered Done.
- A dedicated list is kept and refreshed after every Sprint Review to capture what was not accepted.
- Reasons may include defects, missing functionality, or misinterpretation of requirements; blame is not the focus.
- Next steps are to refine, prioritize, and plan rework via the Product Backlog for a future Sprint.
Example
During Sprint Review, the Product Owner rejects a report feature because export to CSV was missing and performance criteria were not met. The item is added to the Rejected Deliverables list and the Product Backlog is updated with clarified acceptance criteria and a new priority for rework next Sprint.
PMP Example Question
After a Sprint Review, the Product Owner rejects two user stories that did not meet acceptance criteria. What should the Scrum Team do next?
- Extend the Sprint by two days to finish the remaining work.
- Record the items on the Rejected Deliverables list and update the Product Backlog to plan rework in a future Sprint.
- Mark the stories as Done since most criteria were met.
- Close the stories and submit a change request to adjust the scope baseline.
Correct Answer: B — Use the Rejected Deliverables list and update the backlog for rework
Explanation: Items not accepted at the Sprint Review are documented as rejected and returned to the Product Backlog for refinement, prioritization, and planning in a future Sprint.
