KPI Name / Definition | Representation | Tool | Maturity Levels | KPI Calculation | On Hover | Remarks |
Deployment Frequencymeasures how often code is deployed to production | Line chart
| Agile Project Management
| M1: Once in quarter, M2: One per month, M3: One per 2 weeks, M4: One per week, M5: >1 per week | It is calculated as No. of deployments done on a environment in a month
| Month - <<Count>> | |
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: >60% M2: 45-60%, M3: 30-45%, M4: 15-30%, M5: <15% | 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>> |
|
Lead time for changesgauges the speed of software delivery by measuring the duration between a code change and its deployment in production. It provides visibility into the efficiency and effectiveness of the development process. | Line Graph with single-select filter
| JIRA Repos | M1: >3 Months M2: 1-3 Months, M3: <1 Month, M4: < 1 week, M5: < 1 Day | Date Range: <<Lead time in Days>> | ||
Mean time to Recover (MTTR) | JIRA | M1: >1 Week M2: 1 day - 1 week, M3: 12-24 Hours, M4: 1-12 Hours, M5: < 1 Hour |
General
Content
Integrations