Page Comparison

KPI Name / Definition

Representation

Tool

Maturity Levels

KPI Calculation

On Hover

Remarks

Status

Issue Count

measures the overall work taken in a sprint

Line Graph

• Y- Axis - Count

• X- Axis - Sprints

• Aggregation Method - Sum

• Positive trend indication - N/A

Agile Project Management

• Jira

• Azure

No Maturity Trend

It is calculated as No. of stories tagged to a Sprint

Sprint Name: <<Value>>

1. ‘Story count issue type’ is used to identify issues that are considered for Story count issue type

2. Issues defined in the configuration filter our the from the issues mentioned in the Sprint Report (Completed and Not Completed category)

Sprint Velocity

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

Line Graph

• Y- Axis - Count

• X- Axis - Sprints

• Aggregation Method - Sum

• Positive trend indication - N/A

Agile Project Management

• Jira

• Azure

No Maturity Trend

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

Last 5 sprints

Sprint Name: <<Value>>

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)

Sprint Capacity Utilization

depicts the maximum amount of time a team can commit within sprint

Line Graph + Column chart

• Y- Axis - Hours

• X- Axis - Sprints

• Aggregation Method - Sum

• Positive trend indication - N/A

Agile Project Management

• Jira

• Azure

No Maturity Trend

SPRINT CAPACITY UTILIZATION

This KPI is calculated based on 2 parameters

Estimated Hours: It explains the total hours required to complete Sprint backlog. The capacity is defined in KnowHOW

Logged Work: The amount of time team has logged within a Sprint. It is derived as sum of all logged work against issues tagged to a Sprint in Jira

Sprint Name:  <<Value>>

1. Logged work will be represented by line graph whereas Estimated hours are represented by bar graph

2. Estimated hours can be manually entered by users from the Capacity screen in KnowHOW (Settings-->Upload Data-->Capacity)

Sprint Predictability

Average Resolution time

measures average time taken to complete an issue that could be a story or bug etc.

Line Graph

• Y- Axis - Days

• X- Axis - Sprints

• Aggregation Method - Average

• Positive trend indication - Decrease

Agile Project Management

• Jira

• Azure

M1 : => 10 days

M2 : 8-10 days

M3 : 5-8 days

M4 : 3-5 days, 

M5 : <= 3 days

Sum of resolution times of all issues completed in the Sprint/No. of issues completed within a sprint

• It is calculated as a ‘Days’. Fewer the days better is the ‘Speed’

• Maturity of the KPI is calculated based on the average of last 5 values that corresponds with the maturity scale

*If the KPI data is not available for last 5 sprints, the Maturity level will not be shown

Sprint Name: <<Value>>

Overall filter option is configurable at the instance level

Number of Check-ins & Merge requests 

helps in measuring the transparency as well the how well the tasks have been broken down. 

Line Graph

• Y- Axis - Count 

• X- Axis - Days

• Aggregation Method - Sum'

• Positive trend indication - Increase

Agile Project Management

• Repos

M1: 0-2

M2: 2-4

M3: 4-8

M4: 8-16

M5: >16

NUMBER OF MERGE REQUESTS when looked at along with commits highlights the efficiency of the review process

• It is calculated as a Count. Higher the count better is the ‘Speed’

• Maturity of the KPI is calculated based on the latest value

Date: <<Value>>

Mean time to merge

measures the efficiency of the code review process in a a team

Line Graph

• Y- Axis - Hours

• X- Axis - Weeks

• Aggregation Method - Average

• Positive trend indication - Decrease

Agile Project Management

• Repos

M1 : > 48 Hours

M2 : 16 - 48 Hours

M3 : 8 - 16 Hours

M4 : 4-8 Hours, 

M5 : <4 Hours

• It is calculated in ‘Hours’. Fewer the Hours better is the ‘Speed’

• Maturity of the KPI is calculated based on the average of last 5 values that corresponds with the maturity scale

Date Range: <<Hours>

Code Build Time 

measures the time a job takes to build the code. 

Line Graph

• Y- Axis - Min

• X- Axis - Weeks

• Aggregation Method - Average

• Positive trend indication - Decrease

Agile Project Management

• Jenkins

• Bamboo

• Azure

M1 : > 45 min

M2 : 30-45 mins

M3 : 15-30 min

M4 : 5-15 min, 

M5 : <5 min

• It is calculated in  ‘Mins’. Lesser the time better is the ‘Speed’

• Maturity of the KPI is calculated based on the average of last 5 values that corresponds with the maturity scale

Date Range: <<min>>

Lead Time

is the time from the moment when the request was made by a client and placed on a board to when all work on this item is completed and the request was delivered to the client

Visualization: Text + Table

• Y- Axis - Percentage

• X- Axis - N/A

• Aggregation Method - Average

• Positive trend indication - Decrease

Agile Project Management

• Jira

• Azure

Lead time

M1 : > 60 days

M2 : 45-60 days

M3 : 30-45 days

M4 : 10-30 days, 

M5 : <10 days

Intake to DOR

M1 : > 30 days

M2 : 20-30 days

M3 : 10-20 days

M4 : 5-10 days, 

M5 : < 5 days

DOR to DOD

M1 : > 20 days

M2 : 10-20 days

M3 : 7-10 days

M4 : 3-7 days, 

M5 : < 3 days

DOD to Live

M1 : > 30 days

M2 : 15-30 days

M3 : 5-15 days

M4 : 2-5 days, 

M5 : <2 day

It is calculated as the sum of Ideation time, Development time & Release time

Ideation time (Intake to DOR): Time taken from issue creation to it being ready for Sprint

Development time (DOR to DOD): Time taken from start of work on an issue to it being completed in the Sprint as per DOD

Release time (DOD to Live): Time taken between story completion to it going live.

• Each of the KPIs are calculated in 'Days' . Lower the time, better is the speed & efficiency of that phase

Sprint Name: <<Days>>

1. 'Lead time issue type’ is used to identify issues that are considered for Lead time KPI issue type which falls under Jira/Azure Mappings--> Issue type mappings.

2. Mappings ‘Live Status-Lead time', ‘DOR-Lead time’ & 'DOD Status’ are used to identify issue with particular status which falls under Jira/Azure Mappings--> Workflow status mappings.

Commitment Reliability

measures the percentage work completed at the end of a sprint in comparison to the total work in the sprint

Line Graph 

• Y- Axis - Percentage

• X- Axis - Sprints

• Aggregation Method - Average

• Positive trend indication - Increase

Agile Project Management

• Jira

• Azure

M1 - <40%

M2 - 40-60%

M3 - 60-75%

M4 - 75% - 90% , 

M5 - > 90%

It is calculated No. of issues or Size of issues completed/No. of issues or Size of issues committed

• It is calculated as a 'Percentage'. Higher the percentage during a sprint, better forecasting can be done for future sprints

• Maturity of the KPI is calculated based on the average of last 5 values that corresponds with the maturity scale

Sprint Name: <<Percentage Value>>

Delivered: <<Count/Size>>

Committed: <<Count/Size>>