Sprint burndown chart (Scrum)


Why you need this chart

Sprint Burndown Chart is a graphic representation of the rate at which work is completed and how much work remains to be done. The chart helps to assess the likelihood of achieving the sprint goal. By understanding the progress, the team should be able to respond to changes and adapt.

Why we built our own burndown chart

Sprint Burndown Chart extends burndown functionality beyond the standard one:

  • It is available as a gadget on the Jira dashboard, so you are not tight to a particular Scrum Board and its settings.

  • View the burndown chart along with other handy charts in one place, a Jira dashboard. Configure the dashboard the way you want.

  • Get more information about a sprint with additional metrics that give you a complete view of what has happened during a sprint.

  • Know how a team progresses towards a particular goal - filter by release, epic, or custom JQL.

  • Build the burndown chart based on parent and/or sub-task Jira issues.

Chart analysis

Let’s analyze the chart above. This burndown chart is built for team “Omega,” which follows the Scrum process and is currently working in their sprint #2.

Sprint’s length is two weeks. Today is July 22 (Friday). Sprint #2 started on July 11 (Monday) and will complete today, July 22.

The team tracks their sprint progress in story points.

“Remaining work” metric

The green line on the chart is the “Remaining work” metric. You can configure the remaining work to track story points, remaining time, issue count, or any other numeric Jira field.

As mentioned above, team Omega uses story points for tracking their sprint progress. As you see, they initially planned 33 story points of work to be completed in the sprint.

Yesterday (July 21), the team completed all work for the sprint. Today they added the small user story, and therefore, they still have 2 story points to do:

“Total work” metric

The dark-blue line on the chart is the “Total work” metric. This metric shows how the sprint’s scope changes over time. The scope can change by adding and/or removing work, and by changing an estimate.

On the chart, we see that 2 story points of work have been added today:

This happened because the team yesterday ran out of tasks.

“Completed work” metric

The light-blue line on the chart is the “Completed work” metric. It can show cumulative or daily statistics depending on how it's configured.

Daily statistics shows how much work was completed each day:

Cumulative chart looks like reversed “Remaining work” chart:

“Ideal burndown” metric

The grey line on the chart is the “Ideal burndown” metric. This metric shows how much work should be remaining on each day of the sprint if the team would burn the work linearly.

Statistics for the particular day

Sometimes lots of lines on the chart intersect - this is easily solved by hovering over a particular day and checking the pop-up with detailed statistics for the day:

Chart configuration

For the details, please, continue to https://brokenbuild.atlassian.net/wiki/spaces/ARG/pages/3152019457 article.