Scrum Pattern: Track Done

 

  
ContextThe Development Team is within a Sprint and tracks remaining work with a Sprint Burndown Chart, but it is unclear, how many Product Backlog Items (PBIs) will be completed at the end of the Sprint.
ProblemTracking progress with a Sprint Burndown Charts may lead to up to zero Product Backlog Items done in the Sprint.

Tracking progress with a Sprint Burndown Chart is not tracking remaining work. Thus, if the Chart is updated based on done estimation points of each Sprint Backlog Item, it shows how much work has been invested in PBIs, but not how many of them are done.

Forcestoo little/too much transparency regarding effort invested
too little/too much transparency regarding done work
SolutionUpdate the Sprint Burndown Chart only when a Sprint Backlog Item has been done and if the required work to realize all Sprint Backlog Items in the Sprint increases.

The work increases,

  • if new Technical Tasks are found by the Development Team or
  • if the effort of Sprint Backlog Items is considered higher than the initial estimate or
  • if the Development Team asks for additional Product Backlog Items in case the Sprint Backlog has been realized before the Sprint has ended.
Resulting ContextThe Sprint Burndown Charts shows progress the way the Product Owner sees it and the Development Team knows, what is really “done”.

Andreas HeilwagenDieser Artikel wurde von Andreas Heilwagen am 09.05.2011 um 14:21 gepostet und unter Scrum eingeordnet. Sie können Kommentaren über den RSS 2.0-Feed folgen. Das Posting steht unter der Creative Commons-Lizenz wenn nicht anders vermerkt.

Comments are closed.