{"id":5003134,"date":"2015-12-16T21:28:53","date_gmt":"2015-12-17T05:28:53","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&p=5003134"},"modified":"2023-03-12T12:41:02","modified_gmt":"2023-03-12T19:41:02","slug":"burndown-chart","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/burndown-chart\/","title":{"rendered":"Burndown Chart"},"content":{"rendered":"
\n
\n

The team displays, somewhere on a wall of the project room, a large graph relating the quantity of work remaining (on the vertical axis) and the time elapsed since the start of the project (on the horizontal, showing future as well as past). This constitutes an \u201cinformation radiator<\/a>\u201c, provided it is updated regularly. Two variants exist, depending on whether the amount graphed is for the work remaining in the iteration (\u201csprint burndown\u201d) or more commonly the entire project (\u201cproduct burndown\u201d).<\/p>\n<\/div>\n<\/div>\n

Also Known As<\/h2>\n
\n
\n

The term \u201cburn chart\u201d is sometimes encountered, possibly as a generalization covering variants such as the \u201cburn up chart\u201d.<\/p>\n<\/div>\n<\/div>\n

Expected Benefits<\/h2>\n
\n
\n

This practice results in up-to-date project status being not only visible but in fact shoved into the faces of everyone involved: as a result, it encourages the team to confront any difficulties sooner and more decisively. (The corollary is that the chart\u2019s effectiveness depends on being large enough and situated somewhere it cannot help but provoke discussion; an A4 sheet in an out-of-the-way corridor or at the bottom of a drawer does not constitute an adequate implementation.) The simplicity of burndown charts, which can be created on the basis of velocity<\/a>\u00a0history alone, is another factor of their effectiveness.<\/p>\n<\/div>\n<\/div>\n

Common Pitfalls<\/h2>\n
\n
\n

Burndown charts only show the number of story points completed, they do not indicate any changes in the scope of work as measured by total points in the backlog. \u00a0As a result, it\u2019s difficult to tell whether changes in the burndown chart can be attributed to backlog items completed, or simply an increase (or much less likely) a decrease in story points. The burn-up chart resolves this issue by showing a separate line for overall backlog size.<\/p>\n

Neither the burndown nor burnup chart provides any indication of which product backlog items have been completed. This means that a team can have a burndown chart that shows continued progress, but it does not indicate whether the team is working on the correct things. \u00a0For this reason, burndown and burnup charts can only provide an indication of trends rather than giving an explicit indication of whether a team is delivering the right product backlog items.<\/p>\n<\/div>\n<\/div>\n

Origins<\/h2>\n
\n
\n

Burndown charts appear to be entirely original to the\u00a0Scrum\u00a0<\/a>community; the term does not seem to have a prior use elsewhere in relation to managing software projects or other efforts.<\/p>\n