Scrum team velocity
Overview
Velocity Chart for Scrum team shows statistics of completed and (optionally) active sprints from the selected Scrum board.
The details of a sprint can be configured to include the following metrics:
Initial commitment - the total amount of work that was planned for the sprint before its start
Final commitment - the total amount of work that was in the sprint once it was completed
Completed work - the amount of completed work during the sprint
Added work - the amount of work added to the sprint after its start
Removed work - the amount of work removed from sprint after its start
Benefits
The Velocity Chart answers the following questions:
what is the team productivity trend (completed work in different sprints)
what is the team commitment trend (initial commitment vs completed work)
to what extent the sprint scope size is subject to change (initial commitment vs final commitment)
to what extent the sprint scope is subject to change (added work and removed work amounts)
Key features
available as a report and dashboard gadget
configurable sprints
number of sprints
filter by name
based on the date range
configurable estimation
issue count
story points
time estimate
custom number fields (business value, etc)
configurable sprint metrics
chart color
visibility
average line
chart type (bar, line)
configurable scope
filter issues by release, epic
include/exclude sub-tasks
include/exclude main issues
filter by JQL query
How to configure
The configuration settings are grouped into three categories:
Velocity
Issues
Sprints
Velocity settings
Title | The name of the Agile board is displayed on the gadget view as a link to the 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 the estimation field is set to Time Estimate. Time values can be displayed in:
|
Sprint properties | Using Sprint properties you can show the required sprint metrics. The following sprint metrics are available:
The chart icon next to each property controls the visibility of the average line for this metric. |
Average | Average for sprint metrics can be calculated based on all visible sprints or as a moving average based on a specified number of sprints. Available options for moving average are: 2, 3, 4, 5 sprints |
Chart type | Available chart type options are:
|
Value labels | Annotate all sprint metrics with their number values on the chart. |
Issues settings
Sub-tasks | In all Jira Software reports sub-tasks are not included in 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. |
Sprints settings
Sprint count | Using Sprint count you can define how many last completed sprints will be displayed on the chart. Jira administrator can define maximum allowed Sprint count value which cannot be exceeded in all gadgets. |
Active sprints | Show active sprints or no. |
Sprint dates | You can define date range using From and To date fields. Only sprints with the sprint end date in the specified date range will be displayed on the chart. This option is useful if you need the Velocity Chart for some period in the past. |
Sprint filter | Quite often sprints of multiple teams are present on the same Scrum board. In that case, you will get the 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 that match the filter value. Regular expressions can be used as Sprint filter value:
|