Skip to main content

Cancellation of Sprint

Last post 08:41 pm April 13, 2018 by Mustafa Irani
6 replies
09:45 am March 30, 2016

Hi all,

I have some difficulty in understanding the following statement. Hope to get some help.

"When a Sprint is cancelled, any completed and “Done” Product Backlog items are reviewed. If part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete Product Backlog Items are re-estimated and put back on the Product Backlog. The work done on them depreciates quickly and must be frequently re-estimated."

What does the `the work done on them depreciates quickly and must be frequently re-estimated` mean?

Thanks in advance


11:21 am March 30, 2016

> What does the `the work done on them depreciates quickly and must be frequently re-estimated` mean?

Remember that the Definition of Done applies to the increment and not to a Product Backlog Item. The PBI's that were initially planned into a Sprint may or may not be completed by the end of the Sprint, even though the increment meets the DoD.

This means that partially implemented PBI's can be part of a "Done" increment. There will be less work remaining in order to complete those items. However, the work that has been completed so far for a PBI may not be usable until *all* of the work for that PBI is complete. During that delay, the value of the implemented work will depreciate because it is not being put to use and may no longer reflect the latest understanding of scope. The chances of rework being needed will therefore increase, and it will become harder to implement the work that is believed to remain. Estimates must be updated accordingly.


08:29 pm April 12, 2018

If partially implemented PBI's can be part of a "Done" increment which as i understand is a contributor to the"Done" increment then why we say 'the work that has been completed so far for a PBI may not be usable' in the end we always go for an increment thats usable right ?

 


11:47 pm April 12, 2018

An increment must be useful and of release quality. Any undone work which is invested into the increment must not compromise that usability or quality. Incomplete features may be toggled off for example.

Partially completed work represents an unrealized investment which depreciates in value. As such is a potential source of rework and waste, although it can also improve flow across Sprint boundaries.


02:58 am April 13, 2018

Ok so the partially implemented PBI's is something in which work was invested but at then end it was not needed to achieve the current sprint goal.


06:51 am April 13, 2018

Correct. Some of the planned work, for example, may add value to the Sprint Goal but might not be essential to achieving it. Also, if the Goal is achieved early, other unrelated work might then be actioned.


08:41 pm April 13, 2018

Thank you Ian !


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.