...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Table of Contents |
|---|
Recommended Metrics
For a quicker start, if you are overwhelmed with the amount of things to measure, below is a recommendation about a smaller set of measures to start with, based on a nature of your project and/or aspect or measurement.
| Excerpt | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Metrics by Data Source Types
Release and task tracking
...
Summary | Purpose |
|---|---|
Version Control Summary (roll up report over multiple code repositories) | Bird-eye view on key metrics from the source code repository on with ability to drill down. |
Helps find out the most fragile points in the code base / architecture by showing a modification frequency for files in a project code base. | |
Shows the top of biggest commits in a project code base (last 7 / 30 / 90 days) to identify the biggest pain points for code review; the smaller the better. | |
Shows an amount of code lines changed (added, modified, deleted) over last 6 months. | |
Shows a size of individual commits in a project code base per selected GIT repositories (branches) and selected team member(s) for the last 180 days | |
Shows a number of individual commits in a project code base per selected GIT repositories (branches) and selected team member(s) for the last 180 days. | |
Shows the avg speed of new changes being incorporated to a master code due to delays on code reviews. The less the better - means less overhead for dev process/team to handle merges. |
DevOps industry standard metrics
This is a set of measures and metrics described in the "Accelerate" book and summarized in this article.
"Accelerate" DORA metric | Meaning | Relevant metrics in PERF | PERF data sources |
|---|---|---|---|
Deployment frequency | By “deployment” we mean a software deployment to production or to an app store. The reason the frequency of production deployments matters is because it tells you how often you’re delivering something of value to end users and/or getting feedback from users. | Jenkins, GitLab CI | |
JIRA, Rally | |||
Lead Time for changes | The time it takes to go from code committed to code successfully running in production. | Jenkins, GitLab CI | |
Time between Done and Released (use case 12) | JIRA, Rally | ||
JIRA, TFS, Rally | |||
JIRA, TFS, Rally | |||
JIRA, TFS, Rally | |||
Time to restore service | The time to restore service or mean time to recover (MTTR) metric calculates the average time it takes to restore service | Pipeline Mean Time to Recovery | Jenkins, GitLab CI |
Change Failure Rate | A measure of how often deployment failures occur in production that require immediate remedy (particularity, rollbacks). | Jenkins, GitLab CI | |
Jenkins, GitLab CI | |||
Jenkins, GitLab CI | |||
JIRA, Rally |
Per-person metrics
| Warning |
|---|
Disclaimer! Please always remember that 1) Metric is just an indicator. As a manager you always see a bigger context in which you should interpret numbers. 2) Metrics depend heavily on how well you have set up your data sources. Remember: if you set up the rules of interpretation that are right for your project, you will get the right metrics. |
PERF is more focused on Team-level view. Although, there’re a few per-person metrics/widgets available:
...