Skip to content

Burn Your Burn-down Charts

August 5, 2008 by JurgenAppelo

Burndown In many articles on Scrum, the traditional burn-down chart is still depicted as the preferred method for displaying progress in a sprint or project. However, since the introduction of burn-down charts, several improvements have been suggested by leading authors and experts. I agree with each one of them, and my suggestion to you is to try these ideas, and turn your charting practices completely upside-down!

Scope Change
In "Earned-value and Burn Charts" Alistair Cockburn has described that burn-down charts can be inconvenient when trying to depict a change in scope. This may not be a problem for burn charts in sprints (as the scope is not allowed to change during a sprint) but it is quite relevant for charts depicting the total project. Burn-up charts (the mirror image of burn-down charts) are better suited for charting progress for an entire project, because any changes in the top line clearly indicate changes to the total scope.

Bottlenecks
In "Managing with Cumulative Flow Diagrams" David J. Anderson described how these burn-up charts can be further improved by depicting different stages in development. For example: by drawing different lines for work items that have passed the stages of In Progress, Reviewed, Tested and Deployed it is much easier to identify any bottlenecks in your development pipeline. (Bottlenecks manifest themselves as diverging lines in the burn-up chart.)

Burnup  

In this chart, taken from a real project, you can see that our Beta OK and Live OK statuses were falling behind, as compared to the In Progress and Team Review/OK statuses. In this project this meant that, for a short while, work was being reviewed but not being deployed to the beta test environment, possibly for technical reasons. Apparently, this was suddenly corrected around the 10th of June.

Budgets
In "Agile Charts" John Rusk has shown us that burn charts are missing another key ingredient for many project managers. Burn charts tell you whether the project is on schedule, but not whether it is on budget. This is particularly relevant for development shops (including ours) where teams are doing fixed-price projects. John proposed another enhancement, by adding a burned budget line to the charts.

 Budget

In this chart, taken from the same real project, you can see that spending of the budget followed a traditional S-Curve. The project actually finished just below the original estimate (the red line). (Smart people would be able to merge this chart with the burn-up chart. I'm not that smart, so I keep them separate.)

These ideas, and many more, are also described at length in my own paper called "Progress in Three Dimensions" (PDF, 280KB). And if you are convinced that the improved versions are better than the original burn-down charts, then I suggest that you burn your burn-down charts and chart some new territories for measuring progress in your projects!

Comments

Alternative Burndown Format

August 11, 2008 by peterstev, 1 year 26 weeks ago
Comment id: 1755

Hi Jurgen,

Thanks for the summary! I like to use a somewhat different format. Check out Towards a Better Burn Down Chart.

Cheers,

Peter

Great article!

October 8, 2008 by Marcello de Sales (not verified), 1 year 17 weeks ago
Comment id: 1893

I've looked for more information on how to track changes on project scope with Agile charts, and this article has a great list of references...

Thanks,
Marcello

Burn up charts are better

July 27, 2009 by Anonymous (not verified), 28 weeks 1 day ago
Comment id: 2910

Burn up charts provide more info. It's surprising that they aren't used as much. Currently using NXS-7's Task Analytics http://task-analytics.com/ . The charts are good.

Totally agreed

September 27, 2009 by peter (not verified), 19 weeks 2 days ago
Comment id: 3579

I agree these are greate.
I use Ms project and I load ms files in to projectsimple http://www.adept.dk/english for charts. It can also calculates trend of your progress.

You can also use it as projecttool and then use the charts.
Its free.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <b> <i> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <img> <br> <blockquote>
  • Lines and paragraphs break automatically.
  • Web page addresses and e-mail addresses turn into links automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]".

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Image CAPTCHA
Enter the characters (without spaces) shown in the image.

Best of AgileSoftwareDevelopment.com