Difference between revisions of "Release burndown chart"

From Pearl Language
Jump to navigation Jump to search
(Zeroth version.)
 
m (terse/full)
Line 3: Line 3:
|theme=Agile, Scrum
|theme=Agile, Scrum
|context=product development in an agile context, e.g. using {{p|scrum}} or {{p|kanban}}.
|context=product development in an agile context, e.g. using {{p|scrum}} or {{p|kanban}}.
|wish in a single line=You want to keep track of your release planning and manage expectations accordingly.
|goal=visually manage progress so you can adjust planning accordingly
|therefore in a single line=Create and maintain a chart that tracks the burndown of story points at the end of each sprint.
|wish=You want to keep track of your release planning and manage expectations accordingly.
|wish=You want to keep track of your release planning and manage expectations accordingly.
|so=Create and maintain a chart that tracks the burndown of story points during each sprint.
|wish full=You want to keep track of your release planning and manage expectations accordingly.
|background=Having a {{p|release burndown chart}}, updated at the end of each {{p|sprint}}, implies:
|background=Having a {{p|release burndown chart}}, updated at the end of each {{p|sprint}}, implies:


Line 16: Line 17:


All in all, having a {{p|release burndown chart}} gives more “zin” (direction, meaning, utility, lust).
All in all, having a {{p|release burndown chart}} gives more “zin” (direction, meaning, utility, lust).
|therefore=Create and maintain a chart that tracks the burndown of {{p|story points}} at the end of each {{p|sprint}}. Use it to govern the product development process.
|therefore full=Create and maintain a chart that tracks the burndown of {{p|story points}} at the end of each {{p|sprint}}. Use it to govern the product development process.
}}
}}
==Sources==
==Sources==

Revision as of 10:15, 16 June 2013

…product development in an agile context, e.g. using scrum or kanban.

✣  ✣  ✣

You want to keep track of your release planning and manage expectations accordingly.

Having a release burndown chart, updated at the end of each sprint, implies:

  • having a clear product vision;
  • having a good overview of the product as a whole (the whole elephant), providing the needed context for the fine grained user stories that development is working on;
  • having a clear distinction in priority order and value creation (necessity, flexibility, intelligence, luxury); and, based on that:
  • having clear mid term product goals and planning.

From a ‘fractal’ point of view, the release burndown chart is simply one level of scale higher than the sprint burndown chart.

All in all, having a release burndown chart gives more “zin” (direction, meaning, utility, lust).

Therefore:

Create and maintain a chart that tracks the burndown of story points at the end of each sprint. Use it to govern the product development process.

✣  ✣  ✣



✣  ✣  ✣

Sources