Who has the authority to cancel a Sprint?

The Scrum Guide explicitly states that only the Product Owner has the authority to cancel a Sprint. This is a serious decision and should only be made if the Sprint Goal becomes obsolete, rendering the work within the Sprint irrelevant. This might happen due to a sudden shift in market conditions, company strategy, or technology. When a Sprint is cancelled, any completed and "Done" Product Backlog Items are reviewed, and all incomplete items are re-estimated and put back on the Product Backlog.

A. The team members (Development Team) do not have the authority to cancel the Sprint; they are focused on meeting the Sprint Goal.
B. The Scrum Master is a facilitator and coach for the process and does not have the authority to cancel a Sprint.
D. The role of "Project Manager" is not a defined role within the Scrum framework, which instead distributes these responsibilities among the Scrum Team.

1. Schwaber, K., & Sutherland, J. (2020). The Scrum Guide. Scrum.org. p. 9. ("A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint.")

2. Paasivaara, M., Durasiewicz, S., & Lassenius, C. (2008). Using Scrum in a globally distributed project: A case study. Software Process: Improvement and Practice, 13(6), 527-544. https://doi.org/10.1002/spip.402 (The paper discusses the roles in Scrum, reinforcing that the Product Owner is responsible for the product's direction, which implicitly includes the authority to change course by cancelling a Sprint if the goal is obsolete).