Search code examples
agileagile-project-managementburndowncharts

Burndown chart: tasks, features or software metrics?


I'm developing an app for agile projects management, and I'm wondering what is the measure unit of a Burndown Chart... Wikipedia's article states that it measures the number of tasks remaining each period of time, but I've seen people using it with tasks, features, function/use case points...

Is there a measure unit that is considered "right" or standard between these? Or is it all by choice?


Solution

  • Simply, the burndown chart shows work remaining at a point in time.

    The x-axis is usually time and the y-axis is usually work.

    For a Sprint Burndown, time is most often expressed in days and work is expressed in task hours

    For a Release Burndown, time is often expressed in Sprints and work is expressed in Story Points