Previous increment and expanding DOD
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 ?
> 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.
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.