In this episode of our YouTube channel Crisp Agile Academy I talk about Sprint Burndowns. I discuss the value of having one and that it is a tool for the team, not anyone else. I also give examples of different kind of burndowns: Remaining Hours, Remaining Story Points, Remaining Tasks, Things in progress, and Confidence level. I wrap up the episode with a little quiz.
Midway through the clip the quality of the sound drops. This is due to a glitch with the microphone cable and us forgetting to check the recording with a headset. Lesson learned. Will not repeate 🙂 Hope you enjoy it anyway!
2 responses on “Some examples of Sprint Burndowns”
Since we are delivering points, I suspect the chart goes up because more work was discovered and estimates changed. I wonder if it’s really necessary to change an estimate, seems like a waste. Just let it flatline and use the other measures you mentioned. Cycle time seems like a good measure instead – rather then those disconcerting eek moments.
The second chart could mean the team incorrect recorded completion and had to reopen a story and apply more work to it.
The third chart shows the team took on too much work and couldn’t complete.
I think there is some nuance to the reasoning and there could be other factors causing this. I tend to think just board visualization is enough, a burndown is just backup and we can live without it.
P.S. I think I get sneaking suspicion of missing something. Please correct and amend as appropriate.
These all sound like probable reasons to why the burnout came out the way they did. I regulary see all three and there allways are different reasons and history behind them.