| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
Anything that is marked RED, is part of Backlog
KPI Name / Definition | Representation | Tool | Maturity Levels | KPI Calculation | On Hover | Remarks |
Issue Countmeasures the overall work taken in a sprint | Line Graph
| Agile Project Management
| No Maturity Trend | It is calculated as No. of stories tagged to a Sprint | Sprint Name: <<Value>> |
|
Sprint Velocitymeasures 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
| Agile Project Management
| No Maturity Trend | SPRINT VELOCITY calculated as Sum of story points of all stories completed within a Sprint Last 5 sprints | Sprint Name: <<Value>> |
|
Commitment Reliabilitymeasures the percentage work completed at the end of a sprint in comparison to the total work in the sprint | Line Graph
| Agile Project Management
| 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
| Sprint Name: <<Percentage Value>> Delivered: <<Count/Size>> Committed: <<Count/Size>> |
|
Sprint PredictabilityMeasures the percentage the iteration velocity against the average velocity of last 3 iteration. | Line Graph
| Agile Project Management
| M5 - 95% -105% | It is calculated as sprint velocity of the targeted sprint/average sprint velocity of previous 3 sprints | Sprint Name: <<Percentage Value>> | |
Sprint Capacity Utilization |
explains the |
effectiveness of sprint planning and sprint execution. | Line Graph + Column chart
| Agile Project Management
|
M1: <20% M2: 20-40%, M3: 40-60%, M4: 60-80%, M5: >80% | SPRINT CAPACITY UTILIZATION This KPI is calculated based on |
3 parameters and showcases 2 views Available Capacity: It |
depicts the total hours |
available for the Sprint . The capacity |
can defined in KnowHOW. Refer to Capacity Management Estimated 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>> |
|
Sprint Predictability
Average Resolution time
measures average time taken to complete an issue that could be a story or bug etc.
| |
Scope ChurnScope churn explains the change in the scope of sprint since the start of iteration | Line Graph
|
| Agile Project Management
| M1: |
>50% M2: |
30- |
50% M3: |
20- |
30% M4: |
10-20% M5: |
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.<10% | Scope Churn = (Stories added + Stories removed) / Count of Stories in Initial Commitment at the time of Sprint start | Sprint Name: <<Value>> |
|
Planning Accuracymeasures if the team is planning iterations based on either capacity or the historical velocity. | Line Graph
|
|
|
|
| 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
| M5 - 95% -105% | 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
| |
Code Build Timemeasures the time a job takes to build the code. | Line Graph
| Agile Project Management
| M1 : > 45 min M2 : 30-45 mins M3 : 15-30 min M4 : 5-15 min, M5 : <5 min |
| 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>>