Measuring DevOps: The Four Keys Project

Through six years of research, Google’s DevOps Research and Assessment (DORA) team has identified four key metrics that indicate the performance of a software development team. The metrics not only give insight into DevOps performance, but the research indicates that these metrics are actually predictive of improved business outcomes, including profitability, productivity, and customer satisfaction.
Google Cloud Platform has created an open source project to help automate the generation and collection of the metrics. Learn more in this video!
Visit repo here: github.com/GoogleCloudPlatfor...
Timestamps:
0:00​ - Intro
1:10 - Definitions and DORA Background
6:20 - Four Keys Implementation
20:34 - Infrastructure Review and Demo
28:01 - Using the Four Keys Dashboard
32:32 - Get involved!

[@RobertVanDellII]

Immediately digging the energy of Dina presenting this content.

[@mrprabu1983]

Thanks for sharing this experience with us Dina and Dave!!! This allow us to compare ourselves with the industry standards and improve. Love this !!!

[@philipdalen]

This video is worth gold!! Thank you very much Dina and Dave, we are super interested to use this in our organization but the whole architecture is a bit intimeddating and requires a fair amount of investment to wrap your head around. That is why these videos are a great help to understand what you had in mind when you created the project.
It would be very useful to have more shorter practical video's that goes into various aspects of the codebase in a bit more detail. If there is anything I could do to help please let me know :)

[@basoon]

So to clarify if you were working with PRs would "Lead Time to Change" be measured from when your PR was merged to your default branch or when each commit in that PR was committed to the PR's branch?

[@DenisSouza-rp9ed]

Hi Dina. Thanks for this video!
Can I get the list of roles needed for fourkeys to work properly? Our team is considering assigning the owner role for install, but later we want to leave only the specific roles the tool needs.

[@dheerajwaghmode758]

Interesting metrics to measure. Thanks for sharing

[@TristanBailey]

Very useful walk though of these including store them.

[@AdminTimmy]

Hey, I know this video was posted a while ago so not sure I will get a reply, but for lead time: what about teams that use pull requests? For example a commit is made to a branch, they then make a pull request and that gets merged, triggers CI/CD. Would you use the commit from the merge or the first commit of that pull request?

[@ValueRobot]

@@ytdinag Thanks for the presentation. Where the timer starts in Lead time has been a contentious detail in my organization. In your view, why shouldn't Lead Time start as soon as an engineer changes the status of a ticket to "In Progress" vs the first commit?

[@anandud2698]

Hi Dina , Can you tell me whether I can run this whole four-keys project as deployments in Kubernetes and not include GCP in it .And also can I add Prometheus instead of Big Query and get the visualization of the metrics in Grafana

[@sandeepkumar-kr3oo]

@anandud2698 did you make any progress on it? interested in similar setup.

[@san2638]

Thanks🤗

[@JosePolo]

Why the Fourkeys connector is no longer show in DataStudio

[@FarzanasLaw]

Interesting video!!!!

[@guilhermemuradpim7317]

thanks for the tips!! :)

[@mirovaligura]

Hello guys, regarding Change Failure Rate was said that CFR = number of incidents / number of successful deploys.
Isn't that suppose to be CFR = number of successful deploys causing incident / number of successful deploys.
e.g.
Option 1 - less incidents than deploys
Deploys = 10
Deploys caused incident = 1
Incidents = 3
1. case : 3 incidents / 10 deploys = 0.3
vs.
2. case : 1 deploy caused incident / 10 deploys = 0.1
Option 2 - mode incidents than deploys
Deploys = 10
Deploys caused incident = 1
Incidents = 15
1. case : 15 incidents / 10 deploys = 1.5
vs.
2. case : 1 deploy caused incident / 10 deploys = 0.1
Can you correct my understanding pls?

[@robertehni2468]

Thanks for this video, very good 😊
Something is unclear for me regarding Lead Time For Changes: "How long it takes for a commit to get to production".
What is meant by commit? All "git commits", e.g. all 5 commits in a feature branch when the branch gets merged, or all "changes to master", e.g. only the merge commit when merging a feature branch with 5 commits.
Both are very interesting metrics and both are useful but it seems that this difference is not really mentioned anywhere.
What do you think?

[@mohanagnihotri104]

looks like comments are keep disappearing. thanks for sharing this project, this project can help to capture the devops maturity matrices, just wanna know how to pinned down the specific area(s) of improvement od continuous delivery pipeline?

[@amitrangari1975]

at the last step I get "Google hasn't verified this app", when it will be fixed?

[@kevinthomas9925]

Hy , Is there a way we can implement the 4 keys in k8s?

[@sandeepkumar-kr3oo]

@kevinthomas9925
did you figure it out? interested...

[@chern0-]

Really great presentation! Is there any way to access these slides?

[@chern0-]

@@ytdinag thank you! Any plans on adding official AWS support?

[@Bukolajohnson]

seems my comment keeps disappearing