Question

When might a Sprint be abnormally cancelled?

a) Only if all Sprint Goals are fully achieved
b) If the Product Owner decides to cancel it
c) If the Scrum Master is unavailable
d) When the Development Team faces insurmountable obstacles

Answer 1

A Sprint can be abnormally cancelled if the Product Owner finds the Sprint Goals to be obsolete, usually due to significant shifts in business goals or market conditions.

Step-by-step explanation:

A Sprint may be abnormally cancelled in the Scrum framework under certain conditions, specifically if the Product Owner deems it necessary. An abnormal cancellation could occur if the Sprint Goals become obsolete, typically due to changes in business direction or market conditions that render the work being done on the product no longer valuable or relevant. It is not a common occurrence and can be seen as a last resort, as it involves the loss of time and resources invested in the Sprint up to that point.

Options such as the Scrum Master being unavailable or the Development Team facing obstacles are not reasons for abnormal cancellation. The team is expected to self-organize in the absence of the Scrum Master, and challenges faced by the Development Team should be addressed within the Sprint rather than leading to its cancellation.