Publicado el 16 de Octubre de 2014 por Paperback.
Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO.
The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced.
With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined. With the clock ticking, Bill must organize work flow streamline interdepartmental communications, and effectively serve the other business functions at Parts Unlimited.
In a fast-paced and entertaining style, three luminaries of the DevOps movement deliver a story that anyone …
Bill is an IT manager at Parts Unlimited. It's Tuesday morning and on his drive into the office, Bill gets a call from the CEO.
The company's new IT initiative, code named Phoenix Project, is critical to the future of Parts Unlimited, but the project is massively over budget and very late. The CEO wants Bill to report directly to him and fix the mess in ninety days or else Bill's entire department will be outsourced.
With the help of a prospective board member and his mysterious philosophy of The Three Ways, Bill starts to see that IT work has more in common with manufacturing plant work than he ever imagined. With the clock ticking, Bill must organize work flow streamline interdepartmental communications, and effectively serve the other business functions at Parts Unlimited.
In a fast-paced and entertaining style, three luminaries of the DevOps movement deliver a story that anyone who works in IT will recognize. Readers will not only learn how to improve their own IT organizations, they'll never view IT the same way again.
It’s a good way to introduce business and DevOps concepts to folks new to them from either direction. My biggest complaint is that in service of that mission, the storytelling plays out somewhere between a bad case of “plot armor” and “wish fulfillment”.
As a novel, this is as bad as it gets. The dialog is awful, the plot is nonsensical, and the characters are like bizarre cardboard cutouts; totally one-dimensional, yet totally unrealistic.
The message that the book is trying to get across may have been more impactful in 2013, but it feels like ancient history now in 2023. There are better books about DevOps that don't spend hundreds of pages telling a hokey story about why it's important.
Reading this book felt like a dejavu. So many situations the authors describe have happened almost exactly as they describe them. We've made the same mistakes and hopefully have learned from them. It's very well written and relatable. Especially people who've not have worked for 20 years in the industry might find this an interesting read to possibly understand certain situations and avoid some of the mistakes we all use to make along our way.
The Phoenix Project is a seminal read on the accumulation of thoughts and processes surrounding DevOps as we know it today. The story is a fictional take on a workplace that is rife with unplanned work and misuse of the process. You might find it similar to something you see in your organization. It has some great insights and relevant stories you can apply to your own practices. In 2020, these things should be less and less relevant, but in fact, they seem to be more relevant than ever with COVID-19 and companies shifting more and more to the cloud with their digital transformation, demanding quicker time to market, just like Parts Unlimited in the book. The characters used in the book are great, and the protagonist gets the shake at the end. I can't help but think one of the characters, Wes, is a bit over the top. To …
The Phoenix Project is a seminal read on the accumulation of thoughts and processes surrounding DevOps as we know it today. The story is a fictional take on a workplace that is rife with unplanned work and misuse of the process. You might find it similar to something you see in your organization. It has some great insights and relevant stories you can apply to your own practices. In 2020, these things should be less and less relevant, but in fact, they seem to be more relevant than ever with COVID-19 and companies shifting more and more to the cloud with their digital transformation, demanding quicker time to market, just like Parts Unlimited in the book. The characters used in the book are great, and the protagonist gets the shake at the end. I can't help but think one of the characters, Wes, is a bit over the top. To summarize, it's a great read on how you and your organization can start thinking about bringing Development and Operations people closer together and get their decisions aligned, ultimately leading to more quality output and faster.
Otra forma de leer The Goal, esta vez aplicado al mundo IT y con foco en DevOps. Muy recomendable
