gene-kim's first book, written with Kevin Behr and George Spafford (the same trio that later wrote the-phoenix-project). Pre-dates the DevOps movement by five years; written in the ITIL (IT Infrastructure Library) tradition rather than the lean/DevOps tradition.
Content
Four practical phases for implementing ITIL change management:
1. Stabilize the patient — stop the bleeding from uncontrolled changes 2. Catch and release — create a repeatable build process 3. Establish a repeatable build library — configuration management 4. Enable continuous improvement — metrics and measurement
The emphasis on controlling change, measuring change success rates, and building repeatable processes anticipates the DevOps concepts that Kim would later develop. The concern with "fragile artifacts" (systems whose configuration is not known or reproducible) is an early version of what became infrastructure-as-code.
Significance to DevOps History
Sold 250,000+ copies in the ITIL community — a substantial audience for a practitioner handbook. The book established Kim as a credible voice in IT operations before he became a DevOps figure.
The intellectual seeds of The Phoenix Project are visible here: the focus on change management, the concern with unplanned work, and the use of measurement to drive improvement. The ITIL framework was the organizational context Kim was working within before he encountered lean and TOC concepts that would reframe his thinking.
Behr and Spafford are not figures in the DevOps movement in their own right; their contribution is through this book and the-phoenix-project collaboration with Kim.
Limitation
The book operates within ITIL's command-and-control assumptions (change advisory boards, approval gates) that DevOps would later challenge. It represents a transitional moment in Kim's thinking, not a DevOps text in the later sense.