Incomplete Work at the End of a Sprint
Understanding how to handle incomplete work at the end of a Sprint is essential for effective Scrum practice. This article explains the proper approach when a Scrum Team cannot complete its work by the end of the Sprint.
Exam Question
What happens if the Scrum Team cannot complete its work by the end of the Sprint?
(choose the best answer)
A. The Sprint is extended temporarily. Lessons are taken to ensure it doesn’t happen again.
B. The Sprint is extended and future Sprints use this new duration.
C. The Sprint length is unchanged and the Scrum Team continuously learns and adapts.
Correct Answer
C. The Sprint length is unchanged and the Scrum Team continuously learns and adapts.
Explanation
Correct Answer
C. The Sprint length is unchanged and the Scrum Team continuously learns and adapts:
In Scrum, the length of the Sprint remains constant. The Scrum Team does not extend the Sprint if they cannot complete the work. Instead, they reflect on what happened during the Sprint Retrospective and make necessary adjustments to improve in future Sprints. This approach maintains the predictability and rhythm of the Sprint cycle, promoting continuous improvement and learning.
Incorrect Answers
A. The Sprint is extended temporarily. Lessons are taken to ensure it doesn’t happen again:
Extending the Sprint is against Scrum principles. The timebox of the Sprint should be respected to ensure consistency and predictability.
B. The Sprint is extended and future Sprints use this new duration:
Changing the duration of Sprints based on the completion of work disrupts the regular cadence of Scrum. The Sprint length should be consistent to allow the team to adapt and improve their process over time.
Responsibilities in Scrum
- Product Owner: The Product Owner collaborates with the Scrum Team to set clear priorities and ensure that the most valuable work is done first. They should support the team in refining and managing the Product Backlog.
- Scrum Master: The Scrum Master facilitates the Sprint Retrospective to help the team identify and implement improvements. They ensure that the principles of Scrum are upheld, including maintaining the timebox of the Sprint.
- Developers: The Developers are responsible for planning and executing the work within the Sprint. They inspect and adapt their process continuously to improve their performance and meet the Sprint Goal.
Relevance to the PSPO I Exam
Understanding how to handle incomplete work and maintain the Sprint length is crucial for the PSPO I exam. This knowledge demonstrates an appreciation of Scrum principles and the importance of maintaining a consistent Sprint cadence to enable continuous improvement.
Key Takeaways
- The Sprint length is constant and should not be extended.
- The Scrum Team learns and adapts through the Sprint Retrospective.
- Continuous improvement is a core principle of Scrum.
Conclusion
Handling incomplete work by maintaining a consistent Sprint length and focusing on continuous improvement is essential for effective Scrum practice. This approach ensures that the Scrum Team can adapt and improve over time, delivering valuable Increments consistently.

Get ready for the official PSPO I exam
320 PSPO I practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 80 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSPO I exam fee ($200) is paid separately to Scrum.org.
More PSPO I exam questions
- What is the typical size for a Scrum Team?” (PSPO I)
- True or False: Sprint Reviews are an opportunity to collect stakeholder feedback.
- True or False: Dependencies could influence how the Product Owner orders Product Backlog items.
- In the middle of the Sprint, the customer decides that there are 2 new features she wants. The Product Owner could:
- A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
