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


  1. 2.

    Steve Smith Continuous Delivery consultant and trainer Author of “Measuring

    Continuous Delivery” b: e: t: @SteveSmithCD Associated with
  2. 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
  3. 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