Answering: “When can Developers cancel a Sprint?” (PSM I)

Developers cannot cancel a Sprint, because only the Product Owner has that authority. When the work proves harder than expected, the Developers renegotiate scope with the Product Owner instead.

Exam Question

When can Developers cancel a Sprint? (choose the best answer)

• A. When the Product Owner is absent too often.
• B. When functional expectations are not well understood.
• C. They cannot. Only Product Owners can cancel Sprints.
• D. When the selected Product Backlog items for the Sprint become unachievable.
• E. When a technical dependency cannot be resolved.

Correct Answer

C. They cannot. Only Product Owners can cancel Sprints.

Why This Is the Correct Answer

The Scrum Guide states “Only the Product Owner has the authority to cancel the Sprint.” It adds that “A Sprint could be cancelled if the Sprint Goal becomes obsolete.” Every option except C describes a difficulty inside the Sprint, not an obsolete goal. Unclear expectations, blocked dependencies or items that turn out too large are problems the Developers raise and work through with the Product Owner. The Guide expects scope to be clarified and renegotiated as more is learned. Cancelling would waste the work done so far, so it is a rare decision reserved for the person accountable for value.

Why the Other Options Are Wrong

A. When the Product Owner is absent too often. An absent Product Owner is an impediment the Scrum Master should address. It does not give the Developers cancellation authority.

B. When functional expectations are not well understood. Unclear expectations call for more collaboration with the Product Owner, not cancellation.

D. When the selected items become unachievable. The Developers renegotiate scope with the Product Owner to protect the Sprint Goal. Item scope is a forecast.

E. When a technical dependency cannot be resolved. This is an impediment to make transparent. Even if it threatened the Sprint Goal, the Product Owner would make the call.

Exam Tip

For any question about who can cancel a Sprint, the answer is the Product Owner. For why, the answer is an obsolete Sprint Goal.

Key Takeaways

• Only the Product Owner can cancel a Sprint.
• The usual trigger is an obsolete Sprint Goal.
• Difficulties inside a Sprint lead to renegotiating scope, not cancelling.