Skip to main content

Previous increment and expanding DOD

Last post 05:35 am December 25, 2013 by Ian Mitchell
2 replies
08:52 am December 24, 2013

Hello,

How do you deal with your previous increment when the Scrum Team expand the Definition Of Done for higher quality.

If the DOD is made more stringent for the next Sprints, that mean the work performed on the previous Sprints is not respecting the DOD any more.

How do you deal with that ?
Do you add new PBI to iterate over previously "done" PBI ?
Do you tolerate that older PBI have less stringent quality criteria ?
Do you just refactor "on the fly" the previous PBI when needs for enhancement appear ?


09:41 am December 24, 2013

> How do you deal with your previous increment when the
> Scrum Team expand the Definition Of Done for higher quality.

When a Definition of Done is improved, the increase in expected quality may mean a delta increase in scope. Work that has already been done remains done, and the need for additional work has been uncovered. This additional work is essentially a product deficit, and new Product Backlog Items will have to be elicited in order to capture that delta. In short, they are essentially new requirements that have been unearthed due to a recent scope change.


05:35 am December 25, 2013

NB an increase in scope resulting from an improved DoD is likely to include at least some NFR's. This is because the improved DoD should take increments closer to production readiness.


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.