| A | B | C | |
|---|---|---|---|
1 | |||
2 | Sprint Burn Down Templates | ||
3 | |||
4 | Instructions: What are these charts? How do I work them? | ||
5 | |||
6 | Updated 2020 | ||
7 | |||
8 | Classic Agile Iteration Charts | ||
9 | |||
10 | • A Burn DOWN for hours (and a version without this, as it's a bit out of fashion these days) • A Burn UP for story points • A Cumulative flow chart to help you to identify bottlenecks in your workflow. | ||
11 | |||
12 | How do I use this Template? | ||
13 | |||
14 | • Choose "Make a copy" from the "File" menu above. • This will save an editable version to your own Google Drive. • Overwrite the content of the white cells, don't delete rows or the calcs in the grey or coloured cells! • By entering data in the input grids, the charts will just happen • Even if you don't use all of the Cumulative flow, keep track of stories completed in the "Done" row | ||
15 | |||
16 | What do the charts show? | ||
17 | |||
18 | Burn Down | ||
19 | Estimated number of hours remaining to complete the sprint goal. | ||
20 | • Normally updated each day, immediately after the stand-up meeting • The Scrum Master adds up all of the estimated hours remaining on all incomplete user stories • Also shows the total number of hours available to the team in the remaining days of the sprint • So, it's designed whether things are on track, ahead or behind schedule • In recent experience (2020), fewer teams do this. So there's a version here without this chart included | ||
21 | |||
22 | Burn Up | ||
23 | Story points completed daily, throughout a sprint. | ||
24 | • Very similar to the burn down • Rather than tracking work still to be done, it tracks work that has been completed • Shows the accumulation of "Done" story points throughout the course of a sprint. | ||
25 | |||
26 | Cumulative Flow | ||
27 | Tracks: Efficiency through stages in the delivery process | ||
28 | • Highlights workflow bottlenecks, by charting the progress of stories through each stage of the sprint • The coloured bands each represent one stage in the development workflow • In a “pull” system, a widening of a coloured bands will indicate a bottleneck in the phase that follows • It could in practice though (when used in Scrum), indicate a lag in the phase itself | ||
29 | |||
30 | Let me know how you go! | ||
31 | |||
32 | You are free copy this doc, and use it in any way you like. Knock yourself out. It'd be great if you could post a link back to the blog (somewhere) if you find the charts give you some help at work! | ||
33 | http://scrumage.com/ | ||
34 | If you find any errors, or think of ways to improve these charts, don't keep it to yourself. Any feedback at all is great. | ||
35 | |||
36 | Adrian | ||
37 | adrian@fittolani.com | ||
38 |