Skip to main content

Sprint Cancellation [SG2020]

Last post 01:26 am January 9, 2021 by Chris Belknap
5 replies
07:45 pm January 8, 2021

A Sprint can be cancelled if the Sprint Goal becomes obsolete, however, isn't it possible the same thing is applicable if the Product Goal becomes obsolete? Can someone confirm?


08:47 pm January 8, 2021

The Scrum Guide says that during the Sprint no changes are made that would endanger the Sprint Goal, and that the Sprint could be cancelled if the Sprint Goal becomes obsolete. No exception is made to this rule regarding Product Goal volatility.


09:54 pm January 8, 2021

No exception is made to this rule regarding Product Goal volatility.

@Ian Mitchell, I hope I am interpreting this correctly but if the Product Goal changes, then essentially that endangers the Sprint Goal right?

Unless, irrespective of the fact that the Product Goal has changed, then for as long as the Sprint Goal is still relevant to the new Product Goal, the Sprint won't get canceled.

Therefore, is this more of an it depends case?


09:56 pm January 8, 2021

If the Product Goal becomes obsolete, can it implies obsolescence of the Sprint Goal? Is it always the case? Can you imagine a scenario where the Product Goal becomes obsolete, however current Sprint Goal is still valid, thus you shouldn't cancel the Sprint?


11:27 pm January 8, 2021

In any given Sprint, no change should be made regarding the current Product Goal if doing so would put the Sprint Goal at risk. The Sprint is an empirical event and hence the imperative is to preserve it.

The obsolesence of a Product Goal is strictly immaterial to Sprint cancellation, although it is possible that the same underlying contributory factors may also lead to Sprint Goal obsolence and to Sprint cancellation on those grounds.


01:26 am January 9, 2021

Here is a good article on the Product Goal, in the context of the Product Goal being invalidated: https://www.scrum.org/resources/blog/scrum-guide-2020-update-introducing-product-goal

Can a Product Goal change during a Sprint?

For the majority of situations, the Product Goal is described in a way that it will require multiple Sprints to realize. That means, like the Sprint Goal it is likely that the Product Goal does not change during a Sprint. It is possible that the Scrum Team, by doing work discovers something that invalidates the Product Goal, in the same way that a Scrum Team can discover something that invalidates the Sprint Goal. When that happens the context of the situation or the environment the team is working in will influence what happens next. Some teams will stop the Sprint (which is the decision of the Product Owner) and go back to the stakeholders and present their findings. Other Scrum Teams will refine the Product Goal and the Sprint Goal validating them at the next Sprint Review. And other Scrum Teams will do something else. The Scrum Guide does not describe exactly what happens in these situations believing that the Scrum Team will make the right decision depending on the situation.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.