| Table of Contents | ||||
|---|---|---|---|---|
|
...
|
...
|
ℹ
KPI Name | Representation (Single Project) | Tools | Maturity level values | Information IconKPI Calculation | On Hover | ||
|---|---|---|---|---|---|---|---|
Ticket open vs closedrate by type (Ticket openrate by type)Multi-select filter will have issue typesLine + Column graph
Agile Project Management
| N/A | Ticket open vs closed rate by type gives a comparison of new tickets getting raised vs number of tickets getting closed grouped by issue type during a defined period. This can be filtered based on issue type | Line + Column graph
| Agile Project Management
| N/A | , the KPI is considered having a positive trend | Date Range- Count |
Ticket Open vs Closed rate by Priority(Ticket open rate by priority)Multi-select filter will have Prioritygives a comparison of new tickets getting raised vs number of tickets getting closed grouped by priority during a defined period. | Line + Column graph
| Agile Project Management
| N/A | Ticket open vs closed rate by priority gives a comparison of new tickets getting raised vs number of tickets getting closed grouped by priority during a defined period. This can be filtered based on priority If the No. of tickets closed are more than the No. of tickets opened in the latest time period, the KPI is considered having a positive trend | Date Range- Count | ||
Net OpenTicket Count By Priority (Ticket Count By Priority)Multi-select filter will have Priorities Line chart
Agile Project Management
Net Open ticket count by priority measures the overall open tickets during a defined period grouped by priority. It considers the gross open and closed count during a period and then plots the net count Decrease in net open ticket count is considered as positive | Date Range- Count | Net Open Ticket Count By RCA (Ticket Count By RCA)Multi-select filter will have RCA valuescounts | Line chart
| Agile Project Management
| N/ANet | open ticket count by RCA Date Range- Count | |
Net Open Ticket Count By RCA (Ticket Count By RCA)measures the overall open tickets during a defined period grouped by RCA. It considers the gross open and closed count during a period and then plots the net count Decrease in net open ticket count is considered as positive | Date Range- Count | Net Open Ticket count by Status (Total Ticket Count)Multi-select filter will have status | Line chart
| Agile Project Management
| N/ANet | open ticket count by status Date Range- Count | |
Net Open Ticket count by Status (Total Ticket Count)measures the overall open tickets during a defined period grouped by Status. It considers the gross open and closed count during a period and then plots the net count | Line chart
| Agile Project Management
| N/A | Date Range- Count | |||
Open Tickets Ageing by Priority (Total Tickets Aging)Multi-select filter will have Prioritiesgroups all the open tickets based on their ageing and priority | Line chart
| Agile Project Management
| N/A | Open tickets by ageing groups all the open tickets based on their ageing and priority | Date Range- Count | ||
Regression automation Coveragemeasures progress of automation of regression test cases | Line chart
| Agile Project Management
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80% | REGRESSION AUTOMATION COVERAGE measures progress of automation of regression test cases It is calculated as No. of regression test cases automated/Total no. of regression test cases
| Date Range: <<Percentage Value>> Regression test cases automated: <<Value>> Total Regression test cases: <<Value>> | ||
Unit Test CoverageMultiple Project: Multipleis a measurement of the amount of code that is run by unit tests - either lines, branches, or methods | Line Graph with single-select filter Line Graph YY- Axis - Percentage
| Agile Project Management
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80%UNIT TEST COVERAGE is a measurement of the amount of code that is run by unit tests - either lines, branches, or methods. | The calculation is done directly in Sonarqube
| Date Range: << Percentage Value>> | ||
Sonar ViolationsMultiple Project: Stacked Clustered Column with single-select filter Stacked Column Y- Axis - Count X- Axis - Weeks Agile Project Management
| No Maturity Trend | SONAR VIOLATIONS highlight count of issues that exist every time a piece of code breaks a coding rule. The set of coding rules is defined through the associated Quality profile for associated Quality profile for each programming language in the project. | Stacked Column
| Agile Project Management
| No Maturity Trend | The calculation is done directly in Sonarqube. Issues are categorized in 3 types: Bug, Vulnerability and Code Smells All these issues are categorized into 5 type of severity: Blocker, Critical, Major, Minor, Info | Date Range: Blocker: <<Value>> Critical: <<Value>> Major: <<Value>> Minor: <<Value>> Info: <<Value>> |
Sonar Tech DebtMultiple Project: Multiple Line Graph with single-select filterexplains the estimated time required to fix all Maintainability Issues/ code smells | Line Graph
| Agile Project Management
| M1: >100 days M2: 50-100 days M3: 30-50 days, M4: 10-30 days, M5: <10 daysSONAR TECH DEBT explains the estimated time required to fix all Maintainability Issues/ code smells | It is calculated as effort to fix all Code Smells. The effort is calculated in minutes and converted to days by assuming 1 Day=8 Hours
| Date Range:<<Days>> | ||
Test Execution and pass percentageMultiple Project: Multiple Line + Clustered measures the percentage of test cases that have been executed & the percentage that have passed. | Line Graph + Column chart Line Graph
| Agile Project Management
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80% | TEST EXECUTION AND PASS PERCENTAGE measures the percentage of test cases that have been executed & the percentage that have passed. It is calculated as No. of executed test cases out of total test cases in the latest execution during a day/week/month No. of pass test cases out of executed test cases in the latest execution during a day/week/month
| Date Range- <<Percentage Value>> Test Cycle: Executed test cases: <<Value>> Pass test cases: <<Value>> Change Failure RateMultiple Project: Multiple Line Graph with single-select filter Line Graph Y- Axis - PercentageX- Axis - Weeks Aggregation Method - Average Agile Project Management
| M1: >50% M2: 30-50%, M3: 20-30%, M4: 10-20%, M5: <10% | |
CHANGE FAILURE RATE measures the proportion of builds (changes) that have failed for whatever reason over a given period of time It is calculated as Total no. of failed Builds/Total number of Builds
*If the KPI data is not available for last 5 weeks, the Maturity level will not be shown | Date Range: <<Percentage>> Total number of Changes: <<Value>> Failed Changes: <<Value>> | Ticket Velocity | Line Graph
| Agile Project Management
| N/A | Ticket velocity measures the size of tickets (in story points) completed in a defined duration | Date Range- <<Velocity>> |
Team Capacity | Line Graph
| Agile Project Management
| N/A | Team Capacity is sum of capacity of all team member measured in hours during a defined period | Date Range- <<Capacity Hrs>> | ||
Number of Check-inshelps 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: >16NUMBER OF CHECK-INS helps in measuring the transparency as well the how well the tasks have been broken down. |
| Date: <<Value>> | ||
Code Build TimeMultiple Project: Multiple Line Graph with single-select filtermeasures 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 | CODE BUILD TIME measures the time a job takes to build the code.
| Date Range: <<min>> | ||
Lead TimeThe graph will have Radio buttonsis 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 Open to Triage M1 : > 30 days M2 : 20-30 days M3 : 10-20 days M4 : 5-10 days, M5 : < 5 days Triage to Complete M1 : > 20 days M2 : 10-20 days M3 : 7-10 days M4 : 3-7 days, M5 : < 3 days Complete to Live M1 : > 30 days M2 : 15-30 days M3 : 5-15 days M4 : 2-5 days, M5 : <2 dayLEAD 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 | It is calculated as the sum following Open to Triage: Time taken from ticket creation to it being refined & prioritized for development Triage to Complete: Time taken from start of work on a ticket to it being completed by team Complete to Live: Time taken between ticket completion to it going live. Each of the KPIs are calculated in 'Days' | |||
Release FrequencyMultiple Project: Multiple Line Graphhighlights the number of releases done in a month | Line Graph
| Agile Project Management
| No Maturity | RELEASE FREQUENCY highlights the number of releases done in a month It is calculated as number of fix versions in JIRA for a Project that have a Release date falling in a particular month
| Month: <<Count>> | ||
Value delivered (Cost of Delay)Multiple Project: Multiple Line Graphis a prioritization framework that helps a business quantify the economic value of completing a project sooner as opposed to later. | Line Graph
| Agile Project Management
| No MaturityCOST OF DELAY (CoD) is a prioritization framework that helps a business quantify the economic value of completing a project sooner as opposed to later. | It is calculated by adding the following parameters for a Epic or a Feature User-Business Value + Time Criticality + Risk Reduction and/or Opportunity Enablement.
| Month: <<Count>> No. of Epics: <<Count>> |