Forums

By posting to our forums you are agreeing to the Forum terms of use.
Previous increment and expanding DOD
Last Post 25 Dec 2013 04:35 AM by Ian Mitchell. 2 Replies.
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Olivier Ledru
New Member
New Member
Posts:31
Olivier Ledru

--
24 Dec 2013 07:52 AM
    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 ?
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:571
    Ian Mitchell

    --
    24 Dec 2013 08:41 AM
    > 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.
    Ian Mitchell
    Advanced Member
    Advanced Member
    Posts:571
    Ian Mitchell

    --
    25 Dec 2013 04:35 AM
    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.
    You are not authorized to post a reply.


    Feedback