Page Comparison

Definition (Hover Text)

measures the rate at which a team can deliver every Sprint.

Since a stable velocity helps in forecasting, the KPI also measures the last 5 sprints average velocity and plots it along with the sprint velocity

Source Tools

Jira, Azure

Graph type

Line + Column Chart

Filters

-

Hover Format on KPI

Sprint Name: <<Value>>

Fields on Overlay

Sprint Name

Story ID

Issue Description

Size

Business Logic

Calculation Formula

SPRINT VELOCITY calculated as Sum of story points of all stories completed within a Sprint

Average Velocity is captured is the average of last 5 closed sprints

Trend

-

Maturity Levels

Compare Sprint Velocity with Average Velocity

M1: Velocity is 0-40% or >160%

M2: Velocity is 40-60% or 140-160%

M3: Velocity is 60-75% or 125-140%

M4: Velocity is 75-90% or 110-125%

M5: Velocity is 90% -110% - M5

Instance level thresholds

Target KPI value denote 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,406,405)

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.