Release burndown chart
✣ ✣ ✣
You want to keep track of your release planning and manage expectations accordingly.
- 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.
All in all, having a release burndown chart gives more “zin” (direction, meaning, utility, lust).
✣ ✣ ✣
✣ ✣ ✣
Facts about "Release burndown chart"
|Goal||visually manage progress so you can adjust planning accordingly +|
|Pearl||Scrum +, Kanban +, Release burndown chart +, Sprint +, Product vision +, Sprint burndown chart + and Story points +|
|So||Create and maintain a chart that tracks the burndown of story points of each sprint. +|
|Theme||Agile + and Scrum +|
|Wish||You want to keep track of your release planning and manage expectations accordingly. +|