Page Comparison

KPI Name / Definition

Representation

Tool

Maturity Levels

KPI Calculation

On Hover

Remarks

Deployment Frequency

measures how often code is deployed to production

Line chart

• Y- Axis - Count

• X- Axis - Months

• Aggregation Method - Sum

• Positive trend indication - Increase

Agile Project Management

• Build Tools

M1: <1 ,

M2: 1-2,

M3: 2-5,

M4: 5-10,

M5: >10

It is calculated as No. of deployments done on a environment in a month

• It is calculated as a 'Count'. Higher the count during a month, more valuable it is for the Business or a Project

• Maturity of the KPI is calculated based on the latest value

Month - <<Count>> 

Change Failure Rate

measures the proportion of builds (changes) that have failed for whatever reason over a given period of time

Line Graph with single-select filter

• Y- Axis - Percentage

• X- Axis - Weeks

• Aggregation Method - Average

• Positive trend indication - Decrease

Build

• Jenkins

• Bamboo

• Azure Pipelines

• Teamcity

M1: >50% 

M2: 30-50%,

M3: 20-30%,

M4: 10-20%,

M5: <10%

Total no. of failed Builds/Total number of Builds

• It is calculated as a ‘Percentage’. Lower the percentage, better is the ‘Quality’

• 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 weeks, the Maturity level will not be shown

Date Range: <<Percentage>>

Total number of Changes: <<Value>>

Failed Changes: <<Value>>

1. Multiple jobs can be configured for the same project

Lead time for changes

gauges 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

• Y- Axis - Days

• X- Axis - Weeks

• Aggregation Method - Average

• Positive trend indication - Decrease

JIRA

Repos

Date Range: <<Lead time in Days>>

Mean time to Recover (MTTR)