Managing Incomplete Product Backlog Items at the End of a Sprint

In Scrum, it is common for a Scrum Team to encounter situations where a Product Backlog item is not completed by the end of the Sprint. Understanding how to handle these situations is crucial for maintaining the integrity of the Sprint and ensuring continuous delivery of value.

Exam Question

The Developers have not completed a product backlog item by the end of the Sprint.
What should the Scrum Team do with the incomplete product backlog item?

Correct Answer

The incomplete Product Backlog item is returned to the Product Backlog.

Explanation

Handling Incomplete Product Backlog Items

When a Product Backlog item is not completed by the end of the Sprint, it is returned to the Product Backlog for reordering and future consideration. Here’s how this process typically works:

• Return to Product Backlog: The incomplete Product Backlog item is not carried over directly into the next Sprint. Instead, it is returned to the Product Backlog. This allows the Product Owner to decide if it still holds the same value and priority as other items in the Product Backlog.
• Reordering by the Product Owner: Once the incomplete item is back in the Product Backlog, the Product Owner reorders it according to the overall priorities and goals. The Product Owner may choose to prioritize this item for the next Sprint, or it may be reordered lower in the backlog if other items take precedence.
• Re-estimation: If the Product Backlog item is reselected for a future Sprint, it may need to be re-estimated. The Developers consider the remaining work and any new insights gained during the previous Sprint to provide a more accurate estimation.

Key Considerations

• Sprint Goal: The Sprint Goal is a commitment made by the Scrum Team for the Sprint. If the incomplete Product Backlog item is integral to the Sprint Goal, the Scrum Team should discuss the implications during the Sprint Retrospective. This reflection helps them to improve planning and forecasting for future Sprints.
• Continuous Learning: The situation presents an opportunity for the Scrum Team to learn and adapt. The Sprint Retrospective is an excellent time to discuss what led to the incomplete work and how the team can better handle similar situations in the future.

Relevance to the PSM III Exam

Understanding how to manage incomplete work is essential for the PSM III exam, which tests your deep knowledge of Scrum practices and principles. Knowing that incomplete items return to the Product Backlog and are reprioritized is key to maintaining the flow of value in Scrum.

Key Takeaways

• Incomplete items return to the Product Backlog for reordering and future consideration.
• The Product Owner is responsible for deciding the priority of the incomplete item in the context of the overall Product Backlog.
• Sprint Retrospective is crucial for discussing the reasons behind incomplete work and for improving future Sprint planning.

Conclusion

In Scrum, managing incomplete Product Backlog items effectively ensures that the Scrum Team can maintain focus and continuously deliver value. By returning incomplete items to the Product Backlog, the Product Owner can prioritize them based on the overall product goals, and the Scrum Team can improve their processes and forecasting abilities. For more detailed preparation on managing Scrum processes, visit our Scrum Master PSM III™ Exam Prep.