A Sprint can be cancelled by the Product Owner if the Sprint Goal becomes obsolete, meaning it is no longer the highest priority goal due to changes in the market, opportunities, or technical understanding.
Real-world examples of cancelling a Sprint include pursuing a new contract opportunity or realizing that the current goal is not technically feasible, prompting the need to regroup and plan anew.
It is advised not to cancel a Sprint just because the team may not reach the goal on time. Learning from setbacks and adjusting efforts is crucial for understanding the team's capacity and improving its performance.
If a Sprint is cancelled, teams typically try to stick to the original Sprint Review date but may adjust timelines, skip a review, or hold a discussion to inform stakeholders about the cancellation and future plans.