Challenge Your Exam Readiness With Our Free CAPM Practice Questions

Scrum allows the Product Owner to cancel a sprint if the Sprint Goal no longer makes sense—typically because of market shifts, regulatory change, or a strategic pivot that renders the current goal obsolete. Cancellation protects value by avoiding sunk cost on work that no longer advances the Product Goal. A dip in velocity (Option A) is not a reason to cancel; velocity varies and the team adapts its plan to still meet the Sprint Goal. A critical bug (Option C) can be handled by re-planning within the sprint or swapping scope, provided the Sprint Goal remains achievable. Excess stakeholder requests (Option D) are addressed by backlog ordering and negotiation; they don’t invalidate the goal. If cancellation occurs, any completed items meeting the Definition of Done may be reviewed and potentially released. The team then quickly plans a new sprint oriented around the revised goal. CAPM candidates should recognize that cancellation is rare and costly; it should follow a deliberate decision about value, not short-term discomfort.