Burndown charts

Track sprint progress and review past performance over time.

A burndown chart shows how many story points are left in a Scrum team's sprint at the start of each day, from the sprint's start date to its end date. It compares that with the pace needed to finish on time, and during an active sprint it projects whether the team will finish the planned work. Burndown charts are only available for Scrum teams.

A burndown chart follows one sprint day by day. To see how many stories or story points a team completed in each week, month, or sprint, use Story throughput. To see how much work a sprint holds right now, use Total story points.



View the burndown chart

A sprint has a burndown chart once it starts, so future sprints don't have one.


Dedicated burndown page

To see the active sprint's chart, click the burndown chart icon in the header of a Scrum team's In progress page, next to the list and board view icons.


Sprint details dialog

The Sprint details dialog shows the chart for active and completed sprints, in the 'Burndown chart' section at the bottom of the dialog. The section appears once the sprint has at least one item.


From the backlog

  1. Click the ellipsis (...) icon in the sprint header.
  2. Select Sprint details.
  3. Scroll to the 'Burndown chart' section.

From the Sprint calendar

  1. Hover over a sprint and click the ellipsis (...) icon.
  2. Select Edit sprint.
  3. Scroll to the 'Burndown chart' section.


Understand the chart

The vertical axis shows story points, and the horizontal axis shows the sprint's dates. The chart has up to four lines, which the legend below it names:

  • Actual: A solid line with a point for each day up to today, showing the story points remaining in the sprint.
  • Scope: A solid line showing the total story points in the sprint. It steps up or down when stories are added, removed, or resized.
  • Guideline: A dotted line from the sprint's starting scope down to zero on its last day, showing the steady pace that would finish the sprint on time.
  • Projected: A dotted line showing where the sprint is heading if the team keeps its current pace. It only appears for active sprints. For more details, see Projection (active sprints only).

Each point shows the story points remaining at the start of that day, so work completed or added during a day appears on the next day's point. The latest point updates as work changes during the day.

Reading the 'Actual' and 'Scope' lines together tells you why the remaining work changed. When the 'Actual' line drops while the 'Scope' line stays level, the team completed work. When the 'Scope' line moves, stories were added to or removed from the sprint.

If the active sprint has no stories yet, the In progress page shows 'No stories in this sprint yet' instead of a chart.


Hover details

Hover over any day up to today to see a pop-up with:

  • The date.
  • 'Story points remaining'.
  • 'Closed since previous day', when stories were completed.
  • 'Ahead of target' or 'Behind target', showing how many story points the sprint is ahead of or behind the guideline, when there's a difference.
  • 'Story points in scope'.
  • Any stories added to or removed from the sprint, listed under 'Added' and 'Removed' with their Item IDs, titles, and story points. A resized story is listed too.

Once the sprint is halfway through, the pop-up for future days shows the projection instead. For more details, see Projection details.


Scope changes

The 'Scope' line shows the total story points in the sprint at the start of each day. It changes when stories are added to or removed from the sprint, moved into or out of 'Won't do', or resized.

Hover over a day to see which stories were added or removed. The pop-up lists them even when additions and removals cancel each other out, so the total stays the same.

Changes made on the sprint's first day become part of its starting scope, so they aren't listed as additions or removals.


Projection (active sprints only)

During an active sprint, the 'Projected' line shows where the remaining story points are heading if the team keeps its current pace, based on the sprint's progress so far. It appears on the sprint's third day, counting the start date as the first day, and the line and its legend entry are removed when the sprint ends.


Projection details

Once the active sprint is halfway through, hover over the 'Projected' line or any future day to see whether the sprint is on track, ahead, or behind. The pop-up suggests stories to add or lists stories at risk once the team has at least two completed sprints.


On track

'Projection: On track' means the 'Projected' line reaches zero on the sprint's last day. The pop-up shows the sprint's end date as the estimated completion date.


Ahead

'Projection: Ahead' means the 'Projected' line reaches zero before the sprint's last day. The pop-up shows an estimated completion date and how many days early the sprint is projected to finish.

Under 'Stories from backlog that could be completed this sprint', the pop-up suggests stories you could add to the sprint, starting with the next sprint's 'To do' stories in priority order. For how stories are chosen, see How projections are calculated.


Behind

'Projection: Behind' means the 'Projected' line reaches zero after the sprint's last day. The pop-up lists the stories the team may not finish by the sprint's end date, starting with those furthest from done.



Effect of scope changes on the burndown

Adding stories to a sprint increases its scope, while removing them or moving them to 'Won't do' reduces it. Resizing a story changes the scope by the difference in its story points.

Atono shows a warning before you add or remove stories or change the dates of an active or completed sprint, and before you move a completed sprint's story into or out of an 'In progress' or 'Done' step. Click Continue to make the change. If Backlog management is turned on for the team, only its backlog owners, team admins, and people with higher workspace roles can change sprint scope and dates.


Active sprints

Scope changes during an active sprint appear on the 'Scope' line, so you can tell them apart from progress on the planned work. Changing the sprint's start or end date recalculates the chart.


Completed sprints

A completed sprint's 'Scope' line keeps the scope the sprint had when it ended. The 'Actual' line reflects each story's current state, so moving a story out of 'Done' after the sprint ends removes its completion from the chart. Changing a completed sprint's start or end date recalculates the whole chart.



How burndown charts are calculated


What's counted

The chart counts stories only, not bugs. Stories in 'Won't do' aren't counted, but stories marked as outliers are.

A story counts as completed when it moves into a step in the 'Done' workflow category. Moving it between 'Done' steps doesn't change when it was completed. A story that's already done when it's added to the sprint counts as completed on the day it's added.

The chart always reflects each story's current state. A story that's moved out of 'Done' counts as remaining again, and its earlier completion is removed from the chart, as if it had never been completed. If it's completed later, it counts on the day it's completed again.

Each story's points come from its size, using Atono's standard point values, so resizing a story changes the chart.


Team time zone

Days run from midnight to midnight in the team's time zone, which the chart's description names. Every date and daily value on the chart uses it, so all team members see the same chart wherever they are.


Unsized stories

Unsized stories count as the team's average story size, the same estimate that total story points use. For more details, see Unsized stories.

The chart uses the current average each time it's shown, so when the average changes, the chart's values can change too, including on completed sprints.


How projections are calculated


Projected line and status

The 'Projected' line is a straight best-fit line through the sprint's remaining story points, from its start up to today.

The status compares the day the line reaches zero with the sprint's last day, counting only whole days, so a sprint that's projected to finish anywhere on its last day is on track.


Velocity

The suggested and at-risk story lists use the team's average daily velocity, based on the story points completed in its past sprints. Velocity only decides how many stories each list includes, so the 'Projected' line and the status don't depend on it.


Suggested stories

When a sprint is ahead, the pop-up suggests stories that could fit in the time left, based on how many whole days ahead the sprint is and the team's velocity. It looks first at the 'To do' stories in the team's future sprints, in order of each sprint's start date and then each story's position, and then at the 'Unscheduled' section of the team's Backlog. If the next story doesn't fit in what's left, the pop-up adds the first later story that does. Bugs are never suggested.


Stories unlikely to be completed

When a sprint is behind, the pop-up lists the unfinished stories the team is least likely to complete, based on how many story points it's projected to miss. Stories in 'To do' are listed first, then stories in earlier 'In progress' steps, and within a step, stories lower in the list come first. Stories in 'In progress' steps count as unfinished, however far along they are.


Other projections

The Sprint calendar and Story throughput also project a sprint's work, and their numbers can differ from the burndown chart's. The Sprint calendar projects capacity for future sprints from the team's velocity, and Story throughput in sprints view projects the active sprint's total from earlier sprints. The burndown projection uses only the active sprint's own progress.



Did this page help you?