Page Comparison

KPI Name / Definition

Representation

Tool

Maturity Levels

KPI Calculation

On Hover

Remarks

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)

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>>

1. Users can ‘Filter by Issue type’. Upon selection of an issue type from the filter, the trend graph shows the commitment reliability for selected issue type

2. Another filter allows the user to see the delivered percentage w.r.t either

   1. Initial commitment based on Issue count

   2. Initial commitment based on Story Points

   3. Final Scope based on Issue Count

   4. Final Scope based on Story Points

Sprint Predictability

Measures the percentage the iteration velocity against the average velocity of last 3 iteration.

Line Graph 

• Y- Axis - Percentage

• X- Axis - Sprints

• Aggregation Method - Average

• Positive trend indication - Increase

Agile Project Management

• Jira

• Azure

M5 - 95% -105%
M4 - 85-95%, 105-115%
M3 - 75-85%, 115-125%
M2 - 60-75%, 125-140%
M1 - <60%, >140%

It is calculated as

sprint velocity of the targeted sprint/average sprint velocity of previous 3 sprints

Sprint Name: <<Percentage Value>>

Sprint Capacity Utilization

depicts explains the maximum amount of time a team can commit within sprinteffectiveness of sprint planning and sprint execution.

Line Graph + Column chart

• Y- Axis - Hours

• X- Axis - Sprints

• Aggregation Method - Sum

• Positive trend indication - N/A

Agile Project Management

• Jira

• Azure

M1: <20%

M2: 20-40%,

M3: 40-60%,

M4: 60-80%,

M5: >80%

SPRINT CAPACITY UTILIZATION

This KPI is calculated based on 2 parametersEstimated Hours3 parameters and showcases 2 views

Available Capacity: It explains depicts the total hours required to complete Sprint backlogavailable for the Sprint . The capacity is can defined in KnowHOW. Refer to Capacity Management

Logged WorkEstimated Hours: Sum of the estimation of all issues taken in the sprint is considered as Estimated hours

Logged Hours: 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)

3. An additional configuration allows to exclude spilled issues from Estimated Hours and Logged Hours calculation

4. Enhanced to include the Original Estimate added in subtasks when calculating the estimation for the main story. (Release 8.0.0)

Scope Churn

Scope churn explains the change in the scope of sprint since the start of iteration

Line Graph

• Y- Axis - Percentage

• X- Axis - Sprints

• Aggregation Method - Average

• Positive trend indication - Decrease

Agile Project Management

• Jira

• Azure

M1: >50%

M2: 30-50%

M3: 20-30%

M4: 10-20%

M5: <10%

Scope Churn = (Stories added + Stories removed) / Count of Stories in Initial Commitment at the time of Sprint start 

Sprint Name:  <<Value>>

1. Issue type to identify story 

Number of Check-ins & Merge requests 

Planning Accuracy

measures if the team is planning iterations based on either capacity or the historical velocity.

Line Graph

• Y- Axis - Count Story Points/Hrs

• X- Axis - DaysSprints

• Aggregation Method - Sum'

• Positive trend indication - Increase Difference

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

Mean time to merge

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

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>

• Jira

• Azure

M5 - 95% -105%
M4 - 85-95%, 105-115%
M3 - 75-85%, 115-125%
M2 - 60-75%, 125-140%
M1 - <60%, >140%

Based on Average Velocity

Planned work in SP/Average Velocity

Based on Planned Capacity

Planned work/Available Capacity

Sprint

Average Velocity/Planned Capacity - 50 SP or100 Hrs

Planned work - 50 SP or100 Hrs

Under configuration, user gets to select through a radio button

1. Based on Average Velocity

2. Based on Planned Capacity

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>>

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>>