KPI Name / Definition | Representation | Tool | Maturity Levels | KPI Calculation | On Hover | Remarks | Status |
Story 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 | Line Graph
| Agile Project Management
| No Maturity Trend | SPRINT VELOCITY calculated as Sum of story points of all stories completed within a Sprint | Sprint Name: <<Value>> | ||
Sprint Capacity Utilizationdepicts the maximum amount of time a team can commit within sprint | Line Graph + Column chart
| Agile Project Management
| 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>> | ||
Average Resolution timemeasures average time taken to complete an issue that could be a story or bug etc. | Line Graph
| Agile Project Management
| 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
*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 requestshelps in measuring the transparency as well the how well the tasks have been broken down. | Line Graph
| Agile Project Management
| 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
| Date: <<Value>> | ||
Mean time to mergemeasures the efficiency of the code review process in a a team | Line Graph
| Agile Project Management
| M1 : > 48 Hours M2 : 16 - 48 Hours M3 : 8 - 16 Hours M4 : 4-8 Hours, M5 : <4 Hours |
| Date Range: <<Hours> | ||
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>> | ||
Lead Timeis 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
| Agile Project Management
| 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.
| Sprint Name: <<Days>> | ||
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>> |
General
Content
Integrations