Can you explain the concept of a burndown chart?
A burndown chart for an iteration tracks the amount of work the team has left to complete, based on its original estimates, compared with a line drawn from the original amount planned to zero over the days of the iteration. It provides a way to visually track how work is proceeding compared with the original estimate. The chart provides warning signs, for example, the burndown line remains level because no tasks are being completed, or the line goes UP because tasks were needed that weren’t originally anticipated.
Some teams analyze the patterns of their burndown charts over several iterations to see if they might need to try some experiments to change their burndown. For example, if the line consistently goes down, then up near the end of the iteration, then down again, perhaps the team is working on too many stories at one time. If there are unexpected tasks needed in several stories at once, the team will burn “up” instead of down. By focusing on finishing one story at a time, the burndown may track more consistently in the right direction.
Some organizations make a release- or theme-level burndown chart which tracks the amount of work for several iterations, from start to finish of a release or theme. This may help the managers and business stakeholders have confidence about whether all the planned work can be delivered by the target release date, or whether they’ll have to cut scope and reset customer expectations.
Big visible charts are a powerful tool for any team. When we make our process and progress transparent, we’ll be able to identify problems quickly and make corrections to keep ourselves on track. When my own team identifies a problem or impediment in a retrospective, we try to think of some way to make it visible, so we can work on overcoming it. Burndown charts are just one of many useful big visible charts that help Agile teams.
Experiment with burndown charts and other visible tracking tools, and see what works best for your team. You might need different ways of tracking progress as your team improves its process and practices over time.
Dig Deeper on Agile Software Development (Agile, Scrum, Extreme)
Related Q&A from Lisa Crispin
Agile leader Lisa Crispin explains a more organic, more Agile approach to test reporting.continue reading
When it comes to Agile planning, average time over many iterations is a more important metric than individual story estimates.continue reading
Most inexperienced Scrum teams overcommit on what they will deliver, and when. Agile leader Lisa Crispin says that does more harm than good.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.