Who has the ultimate authority to cancel a Sprint?

The ultimate authority to cancel a Sprint lies with the Product Owner. This is primarily because the Product Owner is responsible for maximizing the value of the product and the work done by the Development Team. If the Sprint goal becomes obsolete or if the conditions that justified the Sprint's continuation change significantly, it is the Product Owner's responsibility to assess this scenario and make the decision to cancel the Sprint.

The reasoning behind this authority is also tied to the Scrum framework, in which the Product Owner is the voice of the stakeholders and is charged with ensuring that the team is working on the highest priority items. Should unforeseen circumstances arise—such as significant shifts in market conditions, requirements, or available resources—it is within the Product Owner's purview to cancel the Sprint to preserve value and realign focus.

While the Development Team maintains the ability to assess and discuss the current Sprint goal, and the Scrum Master facilitates the process and addresses challenges, they do not hold the authority to cancel the Sprint. Stakeholders, while important in providing feedback and influencing the Product Owner's decisions, also do not have the authority to cancel the Sprint directly. This structure ensures that the decision remains centralized, promoting swift and effective actions that align with product vision and value generation.