| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
KPI Name / Definition
...
Representation
...
Tool
...
Maturity Levels
...
KPI Calculation
...
On Hover
...
Remarks
Defect Injection Rate
measures the total number of defects (bugs) linked to closed stories which are part of a Iteration.
...
| Table of Contents | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
If anything is marked RED, it is in Backlog
KPI Name / Definition | Representation | Tool | Maturity Levels | KPI Calculation | On Hover | Remarks | ||||||||||||||
Defect Injection Ratemeasures the total number of defects (bugs) linked to closed stories which are part of a Iteration. | Line Graph
| Agile Project Management
| M1: > 175% M2: 175% -125% M3: 125%-75% M4: 75-25% M5: 25% | No. of defects tagged to all stories closed in an iteration/ Total no. of stories closed in the iteration.
| Sprint Name: <<Percentage Value>> Defects: <<Value>> Closed Stories: <<Value>> |
| ||||||||||||||
First time pass ratemeasures the percentage of tickets that pass QA first time (without stimulating a return transition or not having a linked defect) | Line Graph with multi-select filter
| Agile Project Management
| M1 : > 175%<25% M2 : 175% -125% M3: 125%-75% M4: 75-25% M5: 25% No. of defects tagged to all stories closed in an iteration/ Total no. of stories >=25-50% , M3 - >=50-75% , M4 - >=75-90% , M5 - >=90% , | No. of issues closed in a iteration which do not have a return transition or any defects tagged/ Total no. of issues closed in the iteration.
| Sprint Name: <<Percentage Value>> DefectsFTP Stories: <<Value>> Closed Storiesstories: <<Value>> |
First time pass ratemeasures the percentage of tickets that pass QA first time (without stimulating a return transition or not having a linked defect) Line Graph with multi-select filter
| ||||||||||||||
Defect Densitymeasures ratio of the total number of defects (bugs) linked to closed stories and the size of a closed stories | Line Graph
| Agile Project Management
| M1 <25% : > 90% M2 >=25-50% , : 60% -90% M3 - >=50-75% , : 25%-60% M4 - >=75-90% , M5 - >=90% , : 10-25% M5: <10% | No. of issues defects tagged to all stories closed in a iteration which do not have a return transition or any defects tagged/ Total no. of issues closed in the iteration.sprint/ Total size of stories closed in the iteration
| Sprint Name: <<Percentage Value>> FTP StoriesDefects: <<Value>> Total Size of Closed stories : <<Value>> |
| ||||||||||||||
DefectDensitySeepage Ratemeasures ratio of the total number percentage of defects (bugs) linked to closed stories and the size of a closed storiesleaked from the current testing stage to the subsequent stage | Line Graph
| Agile Project Management
| M1 : - > 90%=90% M2 : 60% - >=75-90% M3 : 25%-60% M4: 10-25% M5: <10% No. of defects tagged to all stories closed in a sprint/ Total size of stories closed in the iteration The KPI is applicable only if the estimation is being done in 'Story Points'- >=50-75% , M4 >=25-50% , M5 <25% | No. of valid defects reported at a stage (e.g. UAT)/ Total no. of defects reported in the current stage and previous stage (UAT & QA)
| Sprint Name: <<Percentage Value>> Escaped Defects: <<Value>> Total Size of Closed stories Defects : <<Value>> |
Defect Seepage Ratemeasures the percentage of defects leaked from the current testing stage to the subsequent stage
| ||||||||||||||
Defect Removal Efficiencygives a measure of efficiency of the development team in closing defects raised because of new functionalities within the iteration | Line Graph
| Agile Project Management
| M1 - >=90% <25% M2 - >=7525-90%50% , M3 - >=50-75% , M4 - >=2575-50% 90% , M5 <25% No. of valid defects reported at a stage (e.g. UAT)- >=90% | No. of defects in the iteration that are fixed/ Total no. of defects reported in the current stage and previous stage (UAT & QA)in a iteration
| Sprint Name: <<Percentage Value>> Escaped Closed Defects: <<Value>> Total Defects : <<Value>> Escaped Defects are considered based on the field ‘UAT Defect Identification’ by Labels/CustomField configuration which falls under Jira/Azure Mappings--> Defect Mappings |
Defect Removal Efficiencygives a measure of efficiency of the development team in closing defects raised because of new functionalities within the iteration
| ||||||||||||||
Defect Rejection Ratemeasures the effectiveness of testing team | Line Graph
| Agile Project Management
| M1 <25% - >=75% , M2 - >=2550-50% 75% , M3 - >=5030-75% 50% , M4 - >=7510-90% 30% , M5 - >=90% <10% | No. of defects tagged to stories in the iteration that are fixedrejected / Total no. of defects tagged to stories in a iteration
| Sprint Name: <<Percentage Value>> Closed Rejected Defects: <<Value>> Total Defects : <<Value>> |
Defect Rejection Ratemeasures the effectiveness of testing team Line Graph
| ||||||||||||||
Defect Count by Prioritymeasures number of defects for each priority defined in a project | Line chart
Agile Project Management
| M1 - >=75% , M2 - >=50-75% , M3 - >=30-50% , M4 >=10-30% , M5 <10% | No. of defects tagged to stories in the iteration that are rejected / Total no. of defects tagged to stories in a iteration
| Sprint Name: <<Percentage Value>> Rejected Defects: <<Value>> Total Defects : <<Value>> |
| Defect Count by Prioritymeasures number of defects for each priority defined in a project | No Maturity Trend | No. of defects linked to stories in the iteration grouped by priority
| Sprint Name: P1: <<Value>> P2: <<Value>> P3: <<Value>> P4: <<Value>> |
| Defect Count By RCAmeasures number of defects along with the root cause of defects | Line chart
| No Maturity Trend |
| Regression Automation Coveragemeasures progress of automation of regression test suite in terms of percentage automated out of total regression testcases
| Agile Project Management
| No Maturity Trend | No. of defects linked to stories in the iteration grouped by priority
| Sprint Name: P1: <<Value>> P2: <<Value>> P3: <<Value>> P4: <<Value>> |
|
Defect Count By RCAmeasures number of defects along with the root cause of defects | Line chart
| Agile Project Management
| No Maturity Trend | No. of defects linked to stories in the iteration grouped by Root Cause
| Sprint Name: RCA1: <<Value>> RCA2: <<Value>> RCA3: <<Value>> RCA4: <<Value>> |
| ||||||||||||||
Regression Automation Coveragemeasures progress of automation of regression test suite in terms of percentage automated out of total regression testcases | Line Graph
| Agile Project Management
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80% | No. of regression test cases automated till the end of iteration/Total no. of regression test cases available till the end of iteration
| Sprint Name: <<Percentage Value>> Regression test cases automated: <<Value>> Total Regression test cases: <<Value>> |
| ||||||||||||||
In-Sprint Automation Coveragemeasures progress of automation of test cases linked to stories within the iteration | Line Graph
| Agile Project Management
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80% | No. of regression test cases automated till the end of iteration/Total no. of regression test cases available till the end of linked to stories in iteration that are automated/Total test cases linked to stories in iteration
| Sprint Name: <<Percentage Value>> Regression Linked test cases automated: <<Value>> Total Regression linked test cases: <<Value>> |
| In-Sprint Automation Coveragemeasures progress of automation of test cases linked to stories within the iteration | |||||||||||||
Line GraphTest Execution and pass percentagemeasures the percentage of test cases that have been executed out of the total test cases with an iteration & the percentage that have passed. | Line Graph + Column chart
Agile Project Management
|
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% , M5 - > 80% | No. of executed test cases out of total test cases linked to stories in iteration that are automated/Total test cases linked to stories in iterationin the latest execution of a sprint No. of pass test cases out of executed test cases in the latest execution of a sprint
| Sprint Name: <<Percentage Value>> Test Cycle: Linked Executed test cases automated: <<Value>> Total linked Pass test cases: <<Value>> |
| Test Execution and pass percentagemeasures the percentage of test cases that have been executed out of the total test cases with an iteration & the percentage that have passed. Line Graph + Column chart
| |||||||||||||
Unit Test Coverageis a measurement of the amount of code that is run by unit tests - either lines, branches, or methods | Line Graph with single-select filter
| Code Quality
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% M5 - > 80% No. of executed test cases out of total test cases in the latest execution of a sprint No. of pass test cases out of executed test cases in the latest execution of a sprint> 80% | The calculation is done directly in Sonarqube
| Sprint Name: <<Percentage Value>> Test Cycle: Executed test cases: <<Value>> Pass test cases: <<Value>> |
| Unit Test Coverageis a measurement of the amount of code that is run by unit tests - either lines, branches, or methods | Line Graph with single-select filter
| Date Range: << Percentage Value>> |
| ||||||||||
Sonar Violationshighlight 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 each programming language in the project. | Line chart
| Code Quality
| M1 - <20% M2 - 20-40% M3 - 40-60% M4 - 60% - 80% M5 - > 80% | The calculation is done directly in Sonarqube
| Date Range: << Percentage Value>>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>> |
| ||||||||||||
SonarViolationshighlight 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 each programming language in the project. Line chartTech Debtexplains the estimated time required to fix all Maintainability Issues/ code smells | Line Graph
| Code Quality Date Range: Blocker: <<Value>> Critical: <<Value>> Major: <<Value>> Minor: <<Value>> Info: <<Value>>
| 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 |
| M1: >100 days M2: 50-100 days M3: 30-50 days, M4: 10-30 days, M5: <10 days | 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>> |
| |||||||||||
SonarTech Debtexplains the estimated time required to fix all Maintainability Issues/ code smells LineCode Qualityis graded based on the static and dynamic code analysis procedure built in Sonarqube that analyses code from multiple perspectives. | Bar Graph
| Code Quality
| M1: >100 days E M2: 50-100 daysD M3: 30-50 daysC , M4: 10-30 days, M5: <10 days | 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>>: B, M5: A | Sonar Code Quality is graded based on the static and dynamic code analysis procedure built in Sonarqube that analyses code from multiple perspectives.
| Date Range:<<Months>> |
| ||||||||||||
Change Failure Ratemeasures the proportion of builds (changes) that have failed for whatever reason over a given period of time | Line Graph with single-select filter
| Build
| M1: >50% M2: 30-50%, M3: 20-30%, M4: 10-20%, M5: <10% | 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>> |
| ||||||||||||||
Created vs Resolvedgives an idea about the speed at which the team closes the raised defects. | Line Graph + Column chart
| Agile Project Management
| M1: <20% M2: 20-40%, M3: 40-60%, M4: 60-80%, M5: >80% | Created defects consider all defects which are initially tagged to the Sprint or are added to the sprint in between Closed defects are the completed defects i the sprint out of the created count | Created Defects - <<Value>> Resolved Defects - <<Value>> Resolved Percentage - |