DevOps and the Four Key Metrics

After years of research and data from over 30,000 professionals, the DevOps Research and Assessment (DORA) team identified four key metrics that separate elite teams. In this talk, David Hodge, Google Cloud Certified Architect, will discuss the four key metrics and one way to measure them. More importantly, we will discuss how organizations can adopt the mindset of measuring the metrics and potential pitfalls.

Transcript

1. DORA - DEVOPS RESEARCH AND ASSESSMENT ▸ Six years ▸ 31,000+ professionals worldwide ▸ Various organizations ▸ Nicole Forsgren, PhD ▸ Jez Humble ▸ Gene Kim
2. FOUR KEY METRICS DEVOPS AND THE
5. DAVID HODGE, INDEPENDENT CONSULTANT ▸ eXtreme Programming, agile background ▸ Kaizen mindset ▸ DaveOps Antipattern ▸ Developer/Enterprise Productivity
6. VELOCITY - GET FEATURES TO PRODUCTION ▸Deployment Frequency ▸Lead Time for Changes
7. STABILITY - FEATURES WORK AS EXPECTED ▸Time to Restore Service ▸Change Failure Rate
8. WHY MEASURE Photo by Tsvetoslav Hristov Unsplash
9. DEPLOYMENT FREQUENCY ▸ How often do you deploy to production? ▸ Elite -> On Demand Multiple Times per Day ▸ Basic Ingredients: Number of deployments ▸ How to Measure: Track Number of Deployments ▸ Start simple
10. IF YOU WANT TO KICK HIGHER THEN KICK HIGHER Dan
11. DEPLOYMENT FREQUENCY ▸ Basic Ingredients ▸ Code Repository ▸ Build Pipeline ▸ Monitoring ▸ How to measure ▸ Successful Deployments ▸ Deployment worked ▸ Post deployment checks ▸ Synthetic transactions
12. DEPLOYMENT FREQUENCY - GITLAB ULTIMATE
13. INCREASE DEPLOYMENT FREQUENCY ▸ Do less ▸ Create Tests, Automate
14. DEPLOYMENT FREQUENCY ▸ Obstacles ▸ Permission, Process ▸ Overcome ▸ Blue Green, Canary Deployments ▸ Bake in security in pipeline ▸ Track days waiting for permission
15. DEPLOYMENT FREQUENCY
16. LEAD TIME FOR CHANGES ▸ How long from code commit to production? ▸ Elite ->Less Than a Day
17. LEAD TIME FOR CHANGES ▸ How to measure ▸ Build Pipeline, Release process, Repository commit ▸ Use Ticket management tool to track start and completion (JIRA, Trello) ▸ Quick Test - Make a comment in the code and put it in production
18. Unsplash/Caludia Soraya LEAD TIME FOR CHANGES
19. TIME TO RESTORE SERVICE ▸ How Long Does It Take to resolve service incident or defect ▸ Elite ->Less Than an hour
20. TIME TO RESTORE SERVICE ▸ Basic Ingredients ▸ Monitoring, Logging ▸ Incident Management process ▸ Health checks, Synthetic Transactions ▸ Pre Deployment Checks, Communication across teams ▸ Incident Time Start to End Time
21. CHANGE FAILURE RATE ▸ Percentage of changes to production/released to users result in degraded service ▸ Elite -> 0-15% ▸ Failed Deployment, Hot fi x needed, Rollbacks, Features not correct
22. CHANGE FAILURE RATE ▸ Basic Ingredients ▸ Number of deployments ▸ Number of Incidents per deployment ▸ How to Measure ▸ Honesty - log issues with deployments ▸ De fi ne failure per team
23. CHANGE FAILURE RATE Indiana Jones and the Raiders of the Lost Ark
24. ENTERPRISE ▸ Team Toplogies - Platform, Stream Aligned, Complicated Subsystem, Enabling Team ▸ Enabling Team can scale process vs Each Team Figuring it out ▸ Pilot ▸ Metrics are relevant for a particular team
27. REFERENCES ▸ https://www.devops-research.com/ research.html ▸ https://cloud.google.com/blog/products/ devops-sre/using-the-four-keys-to-measure- your-devops-performance ▸ Accelerate ▸ GitLab
28. QUESTIONS/FEEDBACK ▸ david.hodge@lucidtechnics.com ▸ Of fi ce Hours - https://calendly.com/david- hodge/of fi ce-hours