Skip to main content

Sprint Cancellation

Last post 07:27 am April 16, 2018 by Simon Mayer
4 replies
09:11 pm April 12, 2018

'Sprint cancellations consume resources, since everyone regroups in another Sprint Planning to start another Sprint. Sprint cancellations are often traumatic to the Scrum Team, and are very uncommon.'

As scrum framework helps to realize agility, should not sprint cancellation also be a part of the agility and as scrum team readily accepts and expects changes this should also be considered on similar lines.


11:34 pm April 12, 2018

If Sprint cancellation was normal, wouldn’t goals be less likely to be achieved? What effect might this have on empirical process control in a complex environment?


08:28 pm April 14, 2018

It could be wasteful, depending on the stage when it was cancelled and the applicability of the value of the work done for the upcoming sprints, but its likely to happen for complex projects and the current speed at which the business priorities and needs changes. 


11:34 am April 15, 2018

Sure, agility expects and embraces change. In a Scrum context this means for example that Backlog Items might undergo inspection and adaption. But what if the Sprint's whole goal is obsolete? Lucky enough, this is a rather rare situation. In this case a simple inspection and adaption is not enough. A new Sprint Goal is needed an with it a whole new planning. Only then a new Sprint is needed, canceling the current one.

A simple change in priorities would not make the Sprint Goal obsolete. Given the short duration of a Sprint, the new priorities can be worked on soon enough. Here the Product Owner has an important role to help business develop more stable priorities. 


07:27 am April 16, 2018

As scrum framework helps to realize agility, should not sprint cancellation also be a part of the agility and as scrum team readily accepts and expects changes this should also be considered on similar lines.

Well the option does exist, hence it's described in the Scrum Guide. Agility allows for a quick change of direction, but it doesn't mean you shouldn't know to some extent where you want to go. Frequently having to cancel Sprints suggests a lack of vision about where the product is going.

A Sprint Goal should provide the team with an overriding result that they want to achieve by the end of the Sprint. It is not the same as a list of items from the product backlog. If Sprints are the right length, it should be rare that the goal is no longer wanted during a Sprint or has become significantly less important than something else, even if particular items from the product backlog are no longer wanted or valid.

 


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.