Paperback, 431 pages
English language
Published Feb. 7, 2018 by IT Revolution Press.
The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win is the third book by Gene Kim. The business novel tells the story of an IT manager who has ninety days to rescue an over-budget and late IT initiative, code-named The Phoenix Project.
I genuinely like the writing style. Writing int as a story is definitely infinitely better than any other "recipe" book.
That being said, as of 2024 this book reads full of cliches; and the MC being the macho American ex navy just destroys a bunch of different great points
Has interesting points but not mind blowing (obviously this is 11 years after initial writing)
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.
One step above the typical corporate training video; sort of a casual primer on lean thinking and DevOps. Michael Crichton would’ve made it a lot more interesting.
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.
Someone recommended this to me and I got it for free on Kindle, so I thought I give it a go.
I kind of like the concept of a novelized version of a DevOps book.
I also liked the main characters and the general setup. It seemed a bit weird that a lot of best practices seemed completely unknown in the fictional company, but I guess this might also exist in the real world.
For most of the book I was question myself why I would even read it, it is close enough to what I had to deal with in some of my jobs and I don't really find my life exciting enough to be made into a book.
One of the problems I see is how rapid change is shown in the book. A very large company is turned around in less than a year and this is …
Someone recommended this to me and I got it for free on Kindle, so I thought I give it a go.
I kind of like the concept of a novelized version of a DevOps book.
I also liked the main characters and the general setup. It seemed a bit weird that a lot of best practices seemed completely unknown in the fictional company, but I guess this might also exist in the real world.
For most of the book I was question myself why I would even read it, it is close enough to what I had to deal with in some of my jobs and I don't really find my life exciting enough to be made into a book.
One of the problems I see is how rapid change is shown in the book. A very large company is turned around in less than a year and this is even managed in spite of the awful internal company politics.
A lean & agile management manual written in the form of a novel. Not good as a manual, neither as a novel.
The Phoenix Project is a novel about DevOps. As the story unfolds, we learn what can go wrong in any business’ software projects and how the DevOps movement can help.
For me, a software engineer, it was a very recognizable tale with highs and lows and, eventually, a happy end. Though it is well written, I doubt most people will find it as much of a page turner as I did.
I think it’s a must read for every one who has ever complained about their software department not performing as they would like. There are usually many good and bad reasons for that and not all companies have people in charge that aren’t afraid to make big changes.
