DORA: The 4 Core Metrics: Cycle Time; Lead Time; MTTR; CFR
Problem to solve
It can be difficult to know what to measure from your SDLC. This can lead to wasted effort measuring the wrong thing and the wrong actions being taken.
Intended users
CXO's, VP's, Director's of Engineering. None of our existing Personas listed in the Feature Proposal template.
Further details
We need to support customers in proving the value of using GitLab. By using these 4 metrics, we are leveraging the expertise of Humble, Kim and Forsgren (the DORA 'State of DevOps' team) and their research. A customer can easily compare their teams/organisation against the metrics provided in Accelerate and State of DevOps reports.
Proposal
Very simply, to measure:
-
Cycle Time (planning to production);Deployment Frequency (DF); - Lead Time (commit to production);
- Mean Time to Resolution ('MTTR' - how long to get your code back up and running, if there is an incident);
- Change Failure Rate ('CFR' - % changes going into production that require rework);
And to display them in a separate dashboard/GUI for the user to show them over time/between teams.
Of these I believe MTTR will be the most challenging to measure within GitLab as there is not a concept of an 'incident' in the application yet.
Permissions and Security
Documentation
Testing
What does success look like, and how can we measure that?
What is the type of buyer?
Execs. It should follow the same tier as the rest of the VSM capabilities.