Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How do you know your DevEx Efforts are working?

How do you know your DevEx Efforts are working?

Investing in developer experience as part of your larger platform initiatives is a wise move. But how do you know if your investments are paying off? Traditional DevOps metrics are a good start, but they may not be enough to measure DevEx. To get a complete picture of DevEx, you need to look at it from different levels - team, area, and aggregate. In this talk, Michael Stahnke, co-author of the State of DevOps Report from 2018-2021, will share engineering metrics that truly work and help you determine whether your DevEx program is delivering a positive return on investment. We'll delve into metrics that work for individuals, teams, and departments. The insights shared in this talk are based on experience running sizable sections of engineering at Puppet, CircleCI, and Flox. The metrics and measurements discussed are designed to help any leader or champion of a DevEx program represent the outcomes effectively. While some of the metrics are easy to capture and measure, others require serious investment. Nonetheless, we'll cover them all. If you've been relying on DORA metrics for a while, it's high time you take the next step and explore what's next for measuring engineering effectiveness.

Michael Stahnke

March 15, 2024
Tweet

More Decks by Michael Stahnke

Other Decks in Technology

Transcript

  1. How do you know your DevEx Efforts are working? Michael

    Stahnke VP Engineering at Flox (flox.dev) @stahnma
  2. Availability Cost for Downtime COGS Cost for Services in support

    of Gross Margin Security Attach Rate and dollar value for compliance docs and security questionnaires Developer Productivity Hiring Tradeoffs, time to value, throughput Developer Sentiment Developer Adoption @stahnma
  3. 20

  4. If I add more engineers, will we go faster? Can

    I prove that? 26 @stahnma CFO needs this
  5. 55 Mental Model for Metrics Baseline DevOps Metrics I don’t

    feel elite. Move Quickly with Confidence Throughput Quality Normalization Fungibility Rollbacks (or forwards) Deployments per Week Deploys / Dev / Week Successful deploys Narrow vs Wide Time to 5th PR Changes Understood Start Status Questions @stahnma People Metric Metric Metric Themes
  6. 56 Mental Model for Metrics Baseline DevOps Metrics I don’t

    feel elite. Move Quickly with Confidence Throughput Quality Normalization Fungibility Rollbacks (or forwards) Deployments per Week Deploys / Dev / Week Successful deploys Narrow vs Wide Time to 5th PR Changes Understood Start Status Questions @stahnma People Metric Metric Metric Themes
  7. 57 Mental Model for Metrics Baseline DevOps Metrics I don’t

    feel elite. Move Quickly with Confidence Throughput Quality Normalization Fungibility Rollbacks (or forwards) Deployments per Week Deploys / Dev / Week Successful deploys Narrow vs Wide Time to 5th PR Changes Understood Start Status Questions @stahnma People Metric Metric Metric Themes
  8. Availability Cost for Downtime COGS Cost for Services in support

    of Gross Margin Security Attach Rate and dollar value for compliance docs and security questionnaires Developer Productivity Hiring Tradeoffs, time to value, throughput Developer Sentiment Developer Adoption @stahnma
  9. Summary 59 @stahnma What do you want your metrics to

    tell you? Can you correlate the movement with intentional action and improved outcomes? Do you have baseline metrics already? How have you joined these up with product management? Deploys / Dev / Week is the first metric I would start with after traditional DORA/DevOps metric sets
  10. 60 Twitter’s Engineering Effectiveness Let 1,000 Flowers Bloom - http://

    www.gigamonkeys.com/flowers/ The SPACE of developer Productivity. Research paper from Nicole Forsgren, GitHub Margaret-Anne Storey, University of Victoria Chandra Maddila, Thomas Zimmermann, Brian Houck, and Jenna Butler, Microsoft Research https://queue.acm.org/detail.cfm?id=3454124 GitLab MR Rate https://about.gitlab.com/handbook/engineering/ merge-request-rate/ @stahnma