This repository has been archived by the owner on Nov 17, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathradar.json
12 lines (11 loc) · 2.08 KB
/
radar.json
1
2
3
4
5
6
7
8
9
10
11
12
[
{
"name": "Four key metrics",
"ring": "adopt",
"quadrant": "techniques",
"isNew": "TRUE",
"description": "To measure software delivery performance, more and more organizations are defaulting to the <strong>four key metrics</strong> as defined by the <a ref=\"https://www.devops-research.com/\">DORA research</a> program: change lead time, deployment frequency, mean time to restore (MTTR) and change fail percentage. This research and its statistical analysis have shown a clear link between high-delivery performance and these metrics; they provide a great leading indicator for how a delivery organization as a whole is doing. We're still big proponents of these metrics, but we've also learned some lessons. We're still observing misguided approaches with tools that help teams measure these metrics based purely on their continuous delivery (CD) pipelines. In particular when it comes to the stability metrics (MTTR and change fail percentage), CD pipeline data alone doesn't provide enough information to determine what a deployment failure with real user impact is. Stability metrics only make sense if they include data about real incidents that degrade service for the users. We recommend always to keep in mind the ultimate intention behind a measurement and use it to reflect and learn. For example, before spending weeks building up sophisticated dashboard tooling, consider just regularly taking the <a ref=\"https://www.devops-research.com/quickcheck.html\">DORA quick check</a> in team retrospectives. This gives the team the opportunity to reflect on which <a ref=\"https://www.devops-research.com/research.html#capabilities\">capabilities</a> they could work on to improve their metrics, which can be much more effective than overdetailed out-of-the-box tooling. Keep in mind that these four key metrics originated out of the organization-level research of high-performing teams, and the use of these metrics at a team level should be a way to reflect on their own behaviors, not just another set of metrics to add to the dashboard."
},
{
}
]