DevOps and the Four Key Metrics

Slide 1

Slide 1 text

DORA - DEVOPS RESEARCH AND ASSESSMENT ▸ Six years ▸ 31,000+ professionals worldwide ▸ Various organizations ▸ Nicole Forsgren, PhD ▸ Jez Humble ▸ Gene Kim

Slide 2

Slide 2 text

FOUR KEY METRICS DEVOPS AND THE

Slide 3

Slide 3 text

No content

Slide 4

Slide 4 text

No content

Slide 5

Slide 5 text

DAVID HODGE, INDEPENDENT CONSULTANT ▸ eXtreme Programming, agile background ▸ Kaizen mindset ▸ DaveOps Antipattern ▸ Developer/Enterprise Productivity

Slide 6

Slide 6 text

VELOCITY - GET FEATURES TO PRODUCTION ▸Deployment Frequency ▸Lead Time for Changes

Slide 7

Slide 7 text

STABILITY - FEATURES WORK AS EXPECTED ▸Time to Restore Service ▸Change Failure Rate

Slide 8

Slide 8 text

WHY MEASURE Photo by Tsvetoslav Hristov Unsplash

Slide 9

Slide 9 text

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

Slide 10

Slide 10 text

IF YOU WANT TO KICK HIGHER THEN KICK HIGHER Dan

Slide 11

Slide 11 text

DEPLOYMENT FREQUENCY ▸ Basic Ingredients ▸ Code Repository ▸ Build Pipeline ▸ Monitoring ▸ How to measure ▸ Successful Deployments ▸ Deployment worked ▸ Post deployment checks ▸ Synthetic transactions

Slide 12

Slide 12 text

DEPLOYMENT FREQUENCY - GITLAB ULTIMATE

Slide 13

Slide 13 text

INCREASE DEPLOYMENT FREQUENCY ▸ Do less ▸ Create Tests, Automate

Slide 14

Slide 14 text

DEPLOYMENT FREQUENCY ▸ Obstacles ▸ Permission, Process ▸ Overcome ▸ Blue Green, Canary Deployments ▸ Bake in security in pipeline ▸ Track days waiting for permission

Slide 15

Slide 15 text

DEPLOYMENT FREQUENCY

Slide 16

Slide 16 text

LEAD TIME FOR CHANGES ▸ How long from code commit to production? ▸ Elite ->Less Than a Day

Slide 17

Slide 17 text

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

Slide 18

Slide 18 text

Unsplash/Caludia Soraya LEAD TIME FOR CHANGES

Slide 19

Slide 19 text

TIME TO RESTORE SERVICE ▸ How Long Does It Take to resolve service incident or defect ▸ Elite ->Less Than an hour

Slide 20

Slide 20 text

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

Slide 21

Slide 21 text

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

Slide 22

Slide 22 text

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

Slide 23

Slide 23 text

CHANGE FAILURE RATE Indiana Jones and the Raiders of the Lost Ark

Slide 24

Slide 24 text

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

Slide 25

Slide 25 text

No content

Slide 26

Slide 26 text

No content

Slide 27

Slide 27 text

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

Slide 28

Slide 28 text

QUESTIONS/FEEDBACK ▸ [email protected] ▸ Of fi ce Hours - https://calendly.com/david- hodge/of fi ce-hours