Only Product Owner can cancel a sprint – Scrum Guide
Circumstances for Canceling a Sprint: A Sprint, once started, is typically not canceled. However, there are exceptional cases where it may be necessary:
- Loss of Product Increment Value: If it becomes evident that the work being done in the current Sprint no longer provides value to the product or organization, the Product Owner, in consultation with the development team and Scrum Master, may consider canceling the Sprint.
- External Disruptions: In cases of unforeseen external disruptions like a significant change in market conditions or regulatory requirements that render the Sprint goal irrelevant, the team may decide to cancel the Sprint.
- Unresolvable Issues: If the development team encounters issues or impediments that are insurmountable and prevent them from achieving the Sprint goal, they may, after consultation with the Product Owner and Scrum Master, decide to cancel the Sprint.
Sprint cancellations should be rare and considered as a last resort to ensure that the team remains focused on delivering value, and the decision should be made in collaboration with all relevant stakeholders.