Handling Incomplete Product Backlog Items in Scrum

In Scrum, it’s crucial that work selected for a Sprint meets the Definition of Done by the end of the Sprint. If a Product Backlog item is not completed, specific actions need to be taken. This article explores a specific exam question about handling incomplete Product Backlog items, providing detailed explanations and insights relevant to the PSM II exam.

Exam Question

A Scrum Team selected a Product Backlog item during the Sprint Planning. However, at the end of the Sprint the work does not meet the Definition of Done. What two things should happen with this incomplete Product Backlog item? (choose the best two answers)

• A. Only the stakeholders decide over acceptance of undone work and whether to release it.
• B. The item is not included in the Increment for this Sprint.
• C. Review the item, add the done part of the estimate to the velocity and create a Story for the remaining work.
• D. It is put on the Product Backlog for the Product Owner to decide what to do with it.

Correct Answers

B. The item is not included in the Increment for this Sprint.
D. It is put on the Product Backlog for the Product Owner to decide what to do with it.

Explanation

Correct Answers

B. The item is not included in the Increment for this Sprint: In Scrum, only work that meets the Definition of Done can be considered part of the Increment. Incomplete items do not meet this criteria and thus cannot be included in the Increment delivered at the end of the Sprint. This ensures that the Increment is always potentially shippable and of high quality.

D. It is put on the Product Backlog for the Product Owner to decide what to do with it: Once a Product Backlog item is identified as incomplete, it is returned to the Product Backlog. The Product Owner then re-prioritizes it, considering its importance and the current state of the item. This allows for proper planning and ensures that the item is appropriately addressed in future Sprints.

Incorrect Answers

A. Only the stakeholders decide over acceptance of undone work and whether to release it: This is incorrect because stakeholders do not decide on the acceptance of undone work. The Definition of Done is the standard that determines whether work can be accepted. Stakeholders provide feedback during the Sprint Review, but acceptance is based on the Scrum Team’s adherence to the Definition of Done.

C. Review the item, add the done part of the estimate to the velocity and create a Story for the remaining work: This approach is not aligned with Scrum principles. Velocity should reflect completed work that meets the Definition of Done, not partially completed work. Creating a new story for the remaining work is unnecessary; the incomplete item should be re-prioritized in the Product Backlog.

Responsibilities in Scrum

• Product Owner: The Product Owner is responsible for managing the Product Backlog, ensuring that it is well-ordered and contains items that deliver value. They decide on the prioritization of incomplete items returned to the Product Backlog.
• Scrum Master: The Scrum Master ensures that the Scrum Team adheres to Scrum practices, including the proper handling of incomplete items. They facilitate the Sprint Review and help the team reflect on improvements.
• Developers: Developers are responsible for ensuring that the work selected for the Sprint meets the Definition of Done. They communicate any impediments that prevent completion and collaborate with the Product Owner on re-prioritizing incomplete items.

Relevance to the PSM II Exam

Understanding how to handle incomplete Product Backlog items is crucial for the PSM II exam. It demonstrates advanced knowledge of Scrum principles and the role of the Scrum Team in maintaining a potentially shippable Increment. Mastering this concept ensures that Scrum Masters can effectively guide their teams in adhering to Scrum practices and maintaining high-quality standards.

Key Takeaways

• Incomplete items are not included in the Increment for the Sprint.
• Incomplete items are returned to the Product Backlog for the Product Owner to re-prioritize.
• Adherence to the Definition of Done ensures that the Increment is potentially shippable and of high quality.

Conclusion

Handling incomplete Product Backlog items involves excluding them from the Increment and returning them to the Product Backlog for re-prioritization by the Product Owner. This approach ensures that the Scrum Team maintains high-quality standards and delivers a potentially shippable Increment each Sprint. Understanding these principles is crucial for effective Scrum implementation and success in the PSM II exam. For comprehensive preparation and practice exams, check out PSM II Exam Prep to enhance your understanding and application of Scrum principles.