Metrics and KPIs
info
Properly selected metrics for a project allow for accurate and qualitative assessment of the project and its processes, leading to improvements.
Incorrectly selected metrics, at best, will not help the project, and at worst, will lead to loss of control over the project.
It is important not to seek a silver bullet or blindly copy others' metrics.
This list displays the most commonly encountered basic metrics, their meanings, and areas of application.
| # | Name | Description and Notes | DevOps | Delivery Manager |
|---|---|---|---|---|
| 1 | Deployment Time | - Description: The time taken to deploy a release or other change to the target environment or production. - Notes: It can be calculated separately for release deployments, other changes, and for selected environments. | + | |
| 2 | Deployment Frequency | - Description: The number of deployments over a certain period (e.g., per week or month). - Notes: The usefulness of the metric depends on business requirements and project architecture. The most effective strategy is on-demand delivery. | + | |
| 3 | Deployment Success Rate (Change Failure Rate) | - Description: The percentage of deployments that go without errors or failures. - Notes: The team should agree on what constitutes a failure. This metric helps assess project processes. Deployment Success Rate is the opposite of Change Failure Rate. | + | |
| 4 | Mean Time to Recovery (MTTR) | - Description: The average time required to restore the system after a failure. - Notes: An important aspect of this metric is recording the time of failure and determining when the failure is logged. | + | |
| 5 | Incident Response Time | - Description: The time taken to respond to incidents from the moment they occur. - Notes: A measure of the team's effectiveness in responding to issues and incidents. | + | + |
| 6 | Mean Time Between Failures (MTBF) | - Description: The average time between failures, calculated as the operating time divided by the number of failures. - Notes: Helps identify architectural weaknesses and often works in conjunction with MTTR. | + | |
| 7 | Test Automation Coverage | - Description: The proportion of automated tests out of the total number of tests. - Notes: Besides the automation ratio, it's important to consider the prioritization of cases. | + | |
| 8 | Test Coverage Percentage | - Description: The assessment of code coverage by tests. - Notes: It is necessary to agree with the teams on the coverage percentage to be adopted in the project, usually ranging from 80% to 90%. | + | |
| 9 | Stakeholders Satisfaction Rate | - Description: The assessments of developers' and other CI/CD or end-to-end processes team members' satisfaction. - Notes: It is necessary to identify who the CI/CD and end-to-end processes stakeholders are in the project and to regularly work with their feedback. | + | + |
| 10 | Flow Efficiency | - Description: The percentage of time during which work is actually performed compared to the total time a task spends in the process. - Notes: This metric is highly sensitive to CI/CD process automation and demonstrates the efficiency of end-to-end processes.. | + | + |
| 11 | Lead Time | - Description: The time elapsed from task assignment to its deployment in production. - Notes: This metric serves as an indicator of process quality and helps identify bottlenecks slowing down delivery. | + | + |
| 12 | Cycle Time | - Description: The time taken from the start of task development to its delivery. - Notes: This metric indicates process quality and helps identify development and delivery bottlenecks slowing down work. | + | + |
| 13 | On-time Delivery Rate | - Description: The percentage of projects or tasks completed within the set deadlines. - Notes: An important indicator for assessing a manager's ability to manage timelines and adhere to schedules. | + | |
| 14 | Budget Adherence | - Description: The percentage of projects completed within the allocated budget. - Notes: An assessment of a manager's ability to effectively manage the project's financial resources. | + | |
| 15 | Delivery Quality | - Description: An assessment of the quality of the delivered product or service, based on customer feedback and the number of defects. - Notes: A key indicator of customer satisfaction with product quality. | + | |
| 16 | Communication Efficiency | - Description: The level of team and customer satisfaction with communication efficiency. - Notes: An important aspect for ensuring transparency and coordination among all project participants. | + | |
| 17 | Risk Management Efficiency | - Description: An assessment of the effectiveness of risk management, including the number of identified and successfully mitigated risks. - Notes: Important for understanding how well the team can anticipate and manage potential problems. | + | |
| 18 | Resource Utilization Rate | - Description: The percentage of available resources (human, technical, and financial) utilized in the project. - Notes: Helps determine how efficiently resources are being used. | + | |
| 19 | Scope Changes | - Description: The number and impact of changes to the project's scope. - Notes: Important to monitor how frequently and significantly the project scope changes. | + | |
| 20 | Team Satisfaction | - Description: The level of team members' satisfaction with the project and working conditions. - Notes: High team satisfaction contributes to improved productivity and reduced turnover. | + |