Definition (Hover Text)

Measures the rate at which a team completes work in each sprint.

Source Tools

Jira, Azure Board

Graph type

1. Line graph for Sprint Velocity

2. Column Chart for rolling average velocity

Filters

-

Hover Format on KPI

• Sprint Name

• <<Average velocity Value>>

• <<Sprint velocity Value>>

Fields on Overlay

Sprint Name

Story ID

Issue Description

Size

Business Logic

Calculation Formula

1. SPRINT VELOCITY is calculated as the Sum of story points of all stories completed within the Sprint

2. Average Velocity is the rolling average of the last 5 closed sprints.

Settings

Step 1: Custom Completion Status
Configure the statuses that signify the completion of a work item for your team. The first workflow transition status will be considered if multiple statuses are considered.

Step 2: Issue Types to consider Custom Completion status
Configure the desired issue types that you want to consider for closure.

*Please note:- Global mappings and default Jira statuses will apply if the KPI level settings are not used.

Trend

-

Maturity Levels

NA

Instance level thresholds

Target KPI value denotes the bare minimum project should maintain for KPI

Configurations

Processor Fields

NA

Mandatory fields

NA

How to Validate KPI

Suggested ways of working

1. This KPI calculation is based on the total story points of all issues from the completed issues in the Sprint Report

2. If estimation is configured as Original Estimation for the board, then calculation is based on the total original estimate of all issues from the completed issues in the Sprint Report (Total hours will be converted to story points, i.e., 8 hrs = 1sp)

Sample JQLs

project = "XYZ" AND "SCRUM Team" = ABC AND issuetype = Story AND status in (Closed) AND sprint in(433)

Benefits of KPI

How does the KPI help

1. Helping teams plan better by showing how fast they're working.

2. Spotting trends to work more efficiently.

3. Showing everyone how the sprint is progressing and when it'll be done.