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

Measuring Continuous Delivery

622051376c3b381ef1c786036011112d?s=47 Steve Smith
February 27, 2017

Measuring Continuous Delivery

Continuous Delivery is hard. The breadth and depth of recommended technology and organisational improvements, the smorgasbord of available tools, and the specific circumstances and constraints of your organisation create a huge challenge. Difficult decisions must be made, every single day.

We can reduce uncertainty and make better decisions by measuring the stability and speed of the release process, the build process, and the codebase. These indicators of Continuous Delivery provide quantitative data on the impact of your changes, and pinpoint where the conversations need to happen so you can learn what’s working and what isn’t.

In this talk, Steve Smith will show how measuring stability and speed can power a successful adoption of Continuous Delivery in an organisation of any size. This is a deep dive into the latest thinking on Continuous Delivery, backed up by long-term case studies in private and public sector organisations.


Steve Smith

February 27, 2017

More Decks by Steve Smith

Other Decks in Technology


  1. Measuring Continuous Delivery Steve Smith @SteveSmithCD hello@continuousdeliveryconsulting.com

  2. Steve Smith Continuous Delivery consultant and trainer Author of “Measuring

    Continuous Delivery” b: www.continuousdeliveryconsulting.com e: hello@continuousdeliveryconsulting.com t: @SteveSmithCD Associated with
  3. Continuous Delivery “Speed is essential because there is an opportunity

    cost associated with not delivering software” Dave Farley and Jez Humble Continuous Delivery: when stability and speed can satisfy business demand Discontinuous Delivery: when stability and speed are insufficient
  4. Continuous Delivery

  5. Continuous Delivery

  6. The Improvement Kata

  7. Continuous Delivery Measures “Higher throughput and higher levels of stability

    are possible at scale” DevOps: Profiles in ITSM Performance and Contributing Factors Nicole Forsgren and Jez Humble (WDSI 2016) Continuous Delivery improves throughput and stability in unison Continuous Delivery leads to strong IT performance
  8. Continuous Delivery Measures

  9. Deployment Indicators

  10. Deployment Stability Indicator

  11. Deployment Throughput Indicator

  12. The Government Dept – 60 teams

  13. The Government Dept – 60 teams

  14. Deployment Indicators

  15. Deployment Stability Indicator

  16. Deployment Stability - Apples

  17. Deployment Stability - Apples

  18. Deployment Throughput Indicator

  19. Deployment Throughput - Bananas

  20. Deployment Throughput - Bananas

  21. Build Indicators

  22. Build Stability Indicator

  23. Build Throughput Indicator

  24. Build Indicators

  25. Build Stability Indicator

  26. Build Stability – Grapes

  27. Build Stability – Grapes

  28. Build Throughput Indicator

  29. Build Throughput - Oranges

  30. Build Throughput - Oranges

  31. Code Indicator

  32. Code Throughput Indicator

  33. Code Indicators

  34. Code Throughput Indicator

  35. Code Throughput – Pears

  36. Code Throughput – Pears

  37. The Government Dept – 60 teams

  38. Summary leanpub.com/measuringcontinuousdelivery

  39. Measuring Continuous Delivery Steve Smith @SteveSmithCD hello@continuousdeliveryconsulting.com