Scrum team burnup
Overview
Burnup Chart for Scrum team shows burnup based on completed sprints statistics and projected completion dates based on automatically calculated average and manually entered velocity. The Burnup Chart is based on the selected Scrum board.
Benefits
The Burnup Chart answers the following questions:
- how much work was completed over the last N sprints where N is the configurable option
- how much work remains in the backlog
- what are the projected completion dates and number of sprints based on min, average and max velocity in the last completed sprints
- what are the projected completion date and number of sprints if the velocity of the team is (your value)
- what are the velocity and number of sprints if the completion date is (your value)
How to configure
The configuration settings are split into three categories. Each category is displayed as a separate tab:
- Burnup
- Issues
- Forecast
Burnup settings
| Option | Description |
|---|---|
| Title | The name of the Agile board is displayed on the gadget view as a link to Velocity Chart report of that board. Using Title option you can define a custom name for the link to the board. This can be useful if you have several gadgets based on the same agile board with different configurations for sprints, dates, issue filters or other gadget parameters. |
| Scrum board | Sprints of the selected scrum board will be displayed on the chart. |
| Estimation field | Available options are:
When the board is selected the estimation field is set to board's estimation statistics from its configuration. You can change the default value to any other available estimation if needed. |
| Time unit | Available when estimation field is set to Time Estimate. Time values can be displayed in:
|
| Burnup | |
| Sprint filter | Quite often sprints of multiple teams are present on the same Scrum board. In that case you will get Velocity Chart for sprints of different teams which in most cases is useless. You can filter sprints by name using Sprint filter options to keep only those sprints which match the filter value. Regular expressions can be used as Sprint filter value:
|
| Value labels | Annotate all sprint metrics with their number values on the chart. |
Issues settings
| Option | Description |
|---|---|
| Sub-tasks | In all Jira Software reports sub-tasks are not included into velocity, burnup, burndown statistics. Using this option you can include sub-tasks into sprint metrics calculation. |
| Releases | Filter sprint issues by selected releases. Using this option you can create Release velocity report on sprints basis. |
| Epics | Filter sprint issues by selected epics. Using this option you can create Epic velocity report on sprints basis. |
| JQL filter | Filter sprint issues by custom JQL criteria. Using this option you can create a velocity report for any custom Scrum board scope. |
Forecast settings
In this section, you can adjust how completion forecast is calculated.
By default, the forecast is calculated for the following velocities:
- Max velocity
- Average velocity
- Min velocity
Those velocities are automatically calculated based on the last completed sprints. The number of the completed sprints is defined is Sprint count option.
As values and complete dates of the built-in velocities are calculated automatically their values are displayed as 'auto'.
The completion date can be calculated based on a custom velocity value.
If you provide the desired completion date the required velocity to achieve that goal will be calculated.
| Option | Description |
|---|---|
| Sprint count | The number of last completed sprints to calculate Min, Max and Average automatic velocities which are used in forecast calculation. |
| Sprint length | The length on the future sprints is automatically calculated automatically based on the completed sprints. You can adjust this value to check how it affects the completion date. |
| Remaining work | The remaining work is automatically calculated as a sum of backlog and not completed issues in active sprints. You can adjust this value to check how it affects the completion date. |
| Remaining work growth per sprint | Dynamically change remaining work amount on a sprint by sprint basis to simulate scope change in the future. |
| Start date | The start date of the forecast on the chart. There are two options available:
|