About this report
As the name of the report indicates, the Team Burndowns report displays story point burndown/burnup charts for a selected team. The chart at the top of the page displays the most recent in-progress sprint; the charts below show the last four completed sprints in the selected PI.
If two sprints are active at the same time, the most recent sprint burndown will display on the Team Burndowns page. To see other active sprint burndowns, go to the Team Room, set the desired sprint, and then click the metrics icon to view the burndowns.
These charts represent work remaining/completed versus time; the remaining hours (left) and story points (right) are on the vertical axis, and days in the sprint are on the horizontal axis. These charts are especially useful for Scrum Masters, team leaders and members, and product owners for predicting when all work will be completed by a team; it provides a high-level understanding of whether the work for a sprint is on track. It may be beneficial to review the report with team members and stakeholders during sprint retrospectives and daily standup meetings. This report is generated by selecting a specific program, team, and PI.
Five elements are available on each chart, shown in various colors (colors are set via User Menu > Edit Preferences):
- Dev Complete
- Test Complete
- Ideal Burn
- PI must exist in the system, with sprints defined.
- Features must be created and tied to the PI.
- Stories, with point values, must be created and tied to features.
- Stories must be assigned to sprints.
- Tasks must be created and assigned to stories.
- Tasks ideally should be estimated in hours.
- Teams members must be aligned to target sprints and tasked to stories.
How are report values calculated?
- The horizontal axis displays the range of the sprint, from start date to finish date; this information is defined in the Sprint List/New Sprint panel.
- The vertical axis displays a range for the remaining hours (left) and story points (right), using total hours designated for the sprint and the total count of story points for the sprint.
- Dev Complete = cumulative sum of story points in stories that reached the Dev Complete state during the sprint
- Test Complete = Cumulative sum of story points in stories that reached the Test Complete state during the sprint
- Accepted = cumulative sum of story points in stories that reached the Accepted state during the sprint
- Ideal burn = ideal trajectory needed to accept all story points by the end of the sprint
- Remaining = cumulative sum of story points not completed (to do) in the sprint
How to interpret this report
Assuming the team has estimated stories and tasks accurately and no unforeseen problems have occurred, the Remaining) line should track to the Ideal Burn target. However, some variation around the Ideal Burn line should be expected. Generally, the further the Remaining line rises above the Ideal Burn line, the lower the probability that the team can complete all of the story points defined for the sprint, without adjusting allocations. Keep in mind that the objective of Agile is to maintain the highest sustainable and consistent velocity that is possible over time. Reallocation on a regular basis is less than ideal and should be frowned upon.
As stories are completed and accepted, the Dev Complete, Test Complete, and Accepted lines will trend upwards, typically near the end of the sprint.
Use the results of the charts to make corrections in the upcoming sprint. For example, you may need to leverage the Jira Align planning and estimating tools to improve the quality of your story estimates.