Understanding When a Sprint Might Be Cancelled

In Scrum, the decision to cancel a Sprint is a serious one and is not made lightly. It is only considered when the Sprint Goal becomes irrelevant or unachievable.

Exam Question

When might a Sprint be cancelled?
(choose the best answer)
A. When it becomes clear that not everything will be finished by the end of the Sprint.
B. When the Developers determine the product plan is infeasible.
C. When the sales department has an important new opportunity.
D. When the Sprint Goal becomes obsolete.

Correct Answer

D. When the Sprint Goal becomes obsolete.

Explanation

Correct Answer

D. When the Sprint Goal becomes obsolete:
A Sprint can only be canceled if the Sprint Goal becomes obsolete. This could happen if the goals or priorities of the product change significantly, rendering the current Sprint’s work irrelevant or unnecessary. The Product Owner is responsible for deciding whether to cancel the Sprint, though the decision should be made in consultation with the Scrum Team. Cancellation is a rare occurrence and typically only happens when continuing with the Sprint would no longer deliver valuable outcomes.

Why the Other Options Are Incorrect

A. When it becomes clear that not everything will be finished by the end of the Sprint:
This situation does not warrant canceling the Sprint. Incomplete work can be carried over to the next Sprint or reprioritized during Sprint Planning.

B. When the Developers determine the product plan is infeasible:
If the Developers identify issues with the product plan, the Product Owner might choose to reprioritize the Product Backlog, but this alone does not justify canceling the Sprint unless it directly impacts the Sprint Goal.

C. When the sales department has an important new opportunity:
While an important new opportunity might lead to reprioritization in the Product Backlog, it does not justify canceling a Sprint unless it makes the Sprint Goal obsolete.

Relevance to the PSD Exam

Understanding the conditions under which a Sprint might be canceled is crucial for the PSD exam. It highlights the importance of the Sprint Goal and the Product Owner’s role in maintaining focus and ensuring that the team’s work remains valuable.

Key Takeaways

• Sprint Goal Obsolescence: A Sprint may be canceled if the Sprint Goal becomes obsolete, making the ongoing work irrelevant.
• Product Owner’s Decision: The decision to cancel a Sprint is made by the Product Owner, often in consultation with the Scrum Team.

Conclusion

Canceling a Sprint is a significant decision that should only be made when the Sprint Goal is no longer relevant. This ensures that the Scrum Team’s efforts remain focused on delivering value. For more information on preparing for the PSD exam, visit our Professional Scrum Developer PSD™ Exam Prep.