Handling Undone Product Backlog Items at the End of a Sprint
In Scrum, it is essential to ensure that only work that meets the Definition of Done is considered part of the Increment. If a Product Backlog item does not meet the Definition of Done by the end of a Sprint, specific steps must be taken.
Exam Question
At the end of a Sprint, a Product Backlog item worked on during the Sprint does not meet the Definition of Done. What two things should happen with the undone Product Backlog item?
(choose the best two answers)
A. Put it on the Product Backlog for the Product Owner to decide what to do with it.
B. If the stakeholders agree, the Product Owner can accept it and release it to the users.
C. Do not include the item in the Increment this Sprint.
D. Review the item, add the done part of the estimate to the velocity and create a Story for the remaining work.
Correct Answers
A. Put it on the Product Backlog for the Product Owner to decide what to do with it.
C. Do not include the item in the Increment this Sprint.
Explanation
Correct Answers
A. Put it on the Product Backlog for the Product Owner to decide what to do with it:
If a Product Backlog item is not completed, it should be returned to the Product Backlog. The Product Owner will then re-prioritize it, considering the work needed to finish it in a future Sprint. This ensures that the unfinished item is visible and accounted for in future planning.
C. Do not include the item in the Increment this Sprint:
Only work that meets the Definition of Done can be considered part of the Increment. If an item is not done, it should not be included in the Increment delivered at the end of the Sprint. This maintains the integrity and quality of the Increment.
Why the Other Options Are Less Effective
B. If the stakeholders agree, the Product Owner can accept it and release it to the users:
This option is not aligned with Scrum principles. An item that does not meet the Definition of Done cannot be considered complete or releasable. The Definition of Done ensures quality and completeness, and releasing incomplete work undermines this principle.
D. Review the item, add the done part of the estimate to the velocity and create a Story for the remaining work:
In Scrum, velocity should only reflect the amount of work fully completed according to the Definition of Done. Partially completed work should not be included in velocity calculations. Instead, the item should be re-estimated and planned for completion in a future Sprint.
Importance of the Definition of Done
- Quality Assurance: Ensures that all completed work meets the agreed-upon standards of quality and completeness.
- Transparency: Provides a clear understanding of what work is considered done, fostering transparency within the team and with stakeholders.
- Increment Integrity: Maintains the integrity and usability of the Increment by ensuring only fully completed work is included.
Effective Practices for Managing Undone Work
- Re-Prioritization: Return unfinished work to the Product Backlog and allow the Product Owner to re-prioritize it based on current needs and priorities.
- Re-Estimation: Re-estimate the unfinished work to reflect the effort needed to complete it and plan it in a future Sprint.
- Sprint Review: Use the Sprint Review to discuss what was done and what remains, providing transparency and clarity to stakeholders.
Relevance to the PSU I Exam
Understanding how to handle undone Product Backlog items at the end of a Sprint is crucial for the PSU I exam. It demonstrates knowledge of Scrum principles and the importance of maintaining quality and transparency in product development.
Key Takeaways
- Undone Product Backlog items should be put back on the Product Backlog for re-prioritization by the Product Owner.
- Only work that meets the Definition of Done should be included in the Increment.
- Proper handling of undone work ensures quality, transparency, and integrity of the product.
Conclusion
At the end of a Sprint, if a Product Backlog item does not meet the Definition of Done, it should be returned to the Product Backlog for re-prioritization and not included in the Increment. This approach ensures the quality and integrity of the Increment while providing transparency and maintaining proper planning practices. For more information on preparing for the PSU I exam, visit our Professional Scrum with UX PSU I™ Exam Prep.
