Agile Burndown Charts

A burndown chart is an incredibly powerful, and maybe even more important, simple agile tool for measuring and managing project progress.  Visually, a burndown chart is nothing more than a line chart representing remaining work over time.  Burndown charts are used to measure the progress of an agile project at both a micro and macro level.

  • Micro – Iteration/Sprint burndown charts measure remaining work each day, typically represented in hours, through the life of a single iteration.
  • Macro – Release/Project burndown charts measure the remaining estimate of incomplete product backlog (or user stories) for the entire project or release.  Release burndown charts typically measure remaining points, ideal days, or hours.  A product backlog item/story is considered complete when all of the remaining work has been completed and the tests have passed.
This entry was posted in Agile Development, Agile Metrics. Bookmark the permalink.

6 Responses to Agile Burndown Charts

  1. Javier Lage says:

    Hi, Could you explain how can we set the “Burndown – Remaining To Do” Chart to display the remaining points instead of the remaining task’s hours?

  2. Eli says:

    Hi – is there a way to have our Project Burndown go down when a story is marked “Accepted” without using the “remaining hours estimate”? We have a brand new team and we don’t use points or estimated points. We just want to see a high level burndown that reflects when we are closing stories.

  3. Gayan says:


    Is it possible to view burn down hours by each person per a week?
    If yes, how to do it.

    Thank you

    • admin says:

      Hi Gayan,

      The burndown only focuses on team-level progress. It is not an individual report. However, if you track Effort in your instance, the Member Actuals report will show a total by person of effort logged in a given period.

      Hope this helps,

Leave a Reply

Your email address will not be published. Required fields are marked *