Overview
A burndown chart displays the amount of work in a sprint that still remains and also the work that has been completed. This is a big help for your team because they can handle the progress, predict if they can finish the goals and make them aware of scope changes.
In the horizontal axis (x axis) the period of time in days that the sprint lasts.
In the vertical axis (y axis) the amount of work planned for the sprint, in the unit of measurement chose to estimate: Story points, original time estimate or issue count.
REMOVE DONE BARS DESCRIPTION
Guideline, the grey line. This line is a guide for your team to approximate where they should be to finish the work on time, provided the work was done in a linear progress. The ideal amount of work left or ideal burn rate.
Completed work, the green line. This line indicates the amount of work done (either number of story points completed in the sprint, issues done or time).
Work scope, the blue line. This line is the work planned for the sprint. Here you should check if it increases, which indicates scope creep i.e., growth in the scope of the sprint.
The real amount of work left to be completed in the sprint, based on the unit to estimate the work (story points, original time estimate or issue count) is the distance between the completed work (green line) and the work scope (blue line). When the sprint is finished, both lines should meet.
Configuration
Name your gadget meaningfully, so everyone knows at a glance when to use it. Fill out the rest of the fields as applicable, namely:
The datasource, where Current indicates the Jira cloud instance where the app is installed.
The project and the board where the sprint is. Only works with a single sprint, parallel sprints not supported yet.
The estimation statistic, choose how your team estimates the how much work is committed in a sprint:
Story points. Your team will burn down the story points estimations they did in the backlog.
Original time estimate. Your team will burn down the time estimations they did in the backlog i.e., duration of the issues in hours or days in the Original Estimate field.
Issue count. Your team will burn down the number of issues completed. And they won’t need to enter estimates in the backlog.
Finally, indicate if you want to use the current settings for all the compatible gadgets in the dashboard. This option eases the pain of configuring one by one the rest of the gadgets with the same default configuration
Integrations
(see Jira Software cloud)
We are working on our growing catalog of Gadgets: KPIs and Metrics, but drop us a line in case you want us to expedite a specific one, visit our Help Center.
Dashboards
This gadget appears in the following dashboard: Scrum Software Team template
