The DevOps Handbook: How to Create World-Class Agility, Reliability, and Security in Technology Organizationswriting

gene-kimthree-waysfoundational-textvalue-stream-mapping
2016-10-06 · 1 min read · Edit on Pyrite

The practical companion to the-phoenix-project, written by four of the movement's central figures: gene-kim, jez-humble, patrick-debois, and john-willis. Where The Phoenix Project told a story, the DevOps Handbook provided the implementation guide.

Organization

The book is organized around the three-ways framework that Kim had articulated in the-goal-for-it (2012) and dramatized in The Phoenix Project (2013):

  • Part II: The First Way — Flow (value stream mapping, small batch sizes, continuous integration, deployment pipelines, automated testing)
  • Part III: The Second Way — Feedback (telemetry, monitoring, deployment health, hypothesis-driven development)
  • Part IV: The Third Way — Continual Learning (learning culture, blameless postmortems, scheduling improvement time, chaos engineering)
  • Value Stream Mapping Applied to IT

    The book's opening section adapts value-stream-mapping-for-it from lean manufacturing: mapping the flow from "business hypothesis" to "working software in production" and identifying delays, handoffs, and waste. This was one of the most direct applications of lean thinking to software delivery.

    Case Studies

    Unlike the-phoenix-project's fictional treatment, the DevOps Handbook includes case studies from real organizations: Etsy, Amazon, Google, Netflix, Target, and others. These grounded the practices in documented organizational experience.

    Relationship to Accelerate

    accelerate-book (2018) provides the empirical validation that the DevOps Handbook's practices drive measurable improvements in software delivery performance. The two books are intended to be read together: the Handbook prescribes, Accelerate validates.

    Second Edition (2021)

    A second edition was published in 2021, updating the case studies and adding coverage of platform engineering and security integration (DevSecOps). The core Three Ways framework remained unchanged.

    Intellectual Lineage

    The four authors represent distinct intellectual streams:

  • Kim brings the TOC/lean tradition (Goldratt, Deming)
  • Humble brings the continuous delivery and XP tradition (see continuous-delivery-book)
  • Debois brings the operations/sysadmin tradition and community organizing (DevOpsDays)
  • Willis brings the systems thinking and Deming tradition (see demings-journey-to-profound-knowledge)
  • The book is explicit about its debt to lean manufacturing, Toyota Production System, and Deming — more so than The Phoenix Project.