Skip to main content

The Phoenix Project

Authors: Gene Kim, Kevin Behr, George Spafford
Year: 2013
Genre: Business Novel / DevOps

Overview​

The Phoenix Project is a business novel that follows Bill Palmer, an IT manager who is suddenly asked to fix a critical project called Phoenix — a project that is over budget, behind schedule, and threatening to destroy the entire company.

Through the story, the authors illustrate core principles of DevOps, lean manufacturing, and the Theory of Constraints as applied to IT operations.

Key Concepts​

  • The Three Ways — the foundational principles of DevOps:
    1. Flow — optimizing the flow of work from Development to Operations to the customer.
    2. Feedback — creating fast feedback loops at all stages of the workflow.
    3. Continual Learning and Experimentation — building a culture of experimentation and learning from failures.
  • The Four Types of IT Work — business projects, internal IT projects, changes, and unplanned work.
  • Work-in-Progress (WIP) as a bottleneck — uncontrolled WIP is identified as one of the biggest causes of poor performance.
  • Identifying constraints — applying Goldratt's Theory of Constraints to IT operations.

Why Read It​

This book makes abstract DevOps principles tangible through narrative. It is widely recommended as required reading for anyone in IT operations, development, or leadership roles. It helped popularize the DevOps movement and laid the groundwork for The DevOps Handbook.

  • The DevOps Handbook — Gene Kim et al. (the non-fiction companion)
  • Accelerate — Nicole Forsgren et al.
  • The Goal — Eliyahu M. Goldratt (the inspiration for The Phoenix Project)