The Phoenix Project

A novel about an IT manager named Bill who inherits a catastrophic project and discovers that the principles behind lean manufacturing and agile development can save his department, and his company, from collapse.

Why This One

The Phoenix Project does something remarkable: it makes IT management gripping. Written as a business novel in the tradition of Eliyahu Goldratt’s “The Goal,” it follows Bill Palmer as he is thrust into the role of VP of IT Operations at Parts Unlimited. The Phoenix Project, a critical business initiative, is massively over budget and behind schedule. Bill has ninety days to fix it or his entire department gets outsourced.

Through Bill’s journey, the book introduces the Three Ways: the principles of flow, feedback, and continual learning that underpin both DevOps and agile thinking. You see how work-in-progress limits, deployment pipelines, and cross-functional collaboration emerge not as buzzwords but as survival strategies. The fictional setting lets the authors show what dysfunction looks like before it gets fixed, making the solutions feel earned rather than prescribed.

What to Expect

A 345-page novel that reads like a thriller. No prior technical knowledge is required. The book is particularly powerful for anyone who has worked in or alongside IT and recognizes the chaos it portrays. It complements Scrum by showing the broader organizational context in which agile practices succeed or fail.