This book gives you a holistic understanding of IT operations. Bill Palmer is promoted to vice president of IT at Parts Unlimited, an automotive parts manufactur. “Fresh eyes” if you will. Brent. As in the book, the key constraint was Brent. Summary of The Phoenix Project by Gene Kim, Kevin Behr, and George Spafford | Includes Analysis Preview: The Phoenix Project is a business allegory about how a fictional company becomes profitable after a crisis-driven change in its information technology management style. Unplanned (Firefighting): The most dangerous type of work. A downloadable PDF excerpt from the book  is available from the publisher, IT Revolution Press. This person is represented by a character named Brent. Reviewed in the United States on April 10, 2016. Book review: The Phoenix Project. And just like Bill's team in the book -- we continually learned more about the competing priorities and unknown dependencies in our own company. Gene Kim takes you on an emotional journey from feature discussion with the business to deploying code to production to the chaos that ensues when it all inevitably goes wrong. Object-oriented programming is dead. Suddenly, his boss and his boss’s boss get fired as the company is starting to struggle. Please try your request again later. The state of technology/management books might have been different five years ago, but I found the over-the-top nature insulting to the intelligence of the intended demographic. This sheds some light on why the food chain is structured the way it is. To see what your friends thought of this book, Summary of The Phoenix Project: by Gene Kim, Kevin Behr, and George Spafford | Includes Analysis. Something went wrong. How to Structure Teams for Building Better Software Products, Planned Work — these are typically business projects or new features, Internal Projects — server migrations, software updates and so on, Changes — usually driven by feedback on already completed work, Unplanned Work — support escalations and emergency outages. The authors, Gene Kim, Kevin Behr, and George Spafford, though they use perhaps too much business and military jargon, offer in fictional form, ideas on how to make development and operations work effectively as parts of a team rather than competitors. He likes his team, his level of responsibility, the simple challenges of his day to day work, the work-life balance. To calculate the overall star rating and percentage breakdown by star, we don’t use a simple average. The synopsis is simple. Let us know what’s wrong with this preview of, Published This serves as motivation for me to become one of the top performers. This is an overview of the actual book “The Phoenix Project.“ Kind of like an abbreviated Cliff's Notes for the full book. Our company is at a standstill when they are working on unplanned work. It left me feeling inspired and hopeful for the future. Why? The authors explain DevOps by wrapping it up in a business fable about Parts Unlimited, an auto parts company that DevOps saves. Storyline The narrator is Bill who is … Instead, our system considers things like how recent a review is and if the reviewer bought the item on Amazon. I feel the need for Brent every single day. I like The Phoenix Project because my background is mostly *not* IT, so it was helpful to see the theories put into practice.