Status
Call number
Publication
Description
In this newly updated and expanded edition of the bestselling The Phoenix Project, co-author Gene Kim includes a new afterword and a deeper delve into the Three Ways as described in The DevOps Handbook. Bill, an IT manager at Parts Unlimited, has been, tasked with taking on a project critical to the future of the business, code named Phoenix Project. But, the project is massively over budget and behind schedule. The CEO demands Bill must 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 a manufacturing plant work than he ever imagined. With the clock ticking, Bill must organize workflow 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.… (more)
User reviews
Good luck on getting management to play along.
The book is written in story form which makes it an easy read. Sometimes I struggle to read non-fiction books related to my job, but this one was a breeze to get through and was actually engaging. I even found myself having trouble putting it down a few times!
The back part of the book is also very useful; this is an appendix of sorts that goes through various Dev Ops and IT tools.
Overall I thought this was a great intro to Dev Ops that was very approachable and easy to read. I would recommend to people who are relatively new to the idea or field. This is a great primer that’s written in an entertaining way.
Too often, those in IT keeps their ears closed to their fellow co-workers; not surprisingly, those outside of IT do not keep up with software developments either. This book illustrates how to overcome those silos with mere curiosity.
Most organizations – even those outside of traditional tech-sector jobs – can die without effective information management. Through an interesting (and all too typical) narrative, this book illustrates how to make information technology, to buy a metaphor from anatomy, the nervous system of your organizations.
Like all great literature, this story plays upon universal human themes like coming together, listening to each other, and solving huge problems in unconventional ways. It conveys these truths in a way that computer programmers like me can relate to their jobs. I’ve heard and seen most of the bad practices in this book; I’ve also seen many of the suggested solutions in practice in my colleagues. I leave this book ready to encounter the new challenges at my work on Monday morning.
Now, here’s to hoping that I can take the inspiration gathered in this book and apply it to my software launch!
The book starts with a description that many IT departments would find familiar. And then progressively moves towards "10 deploys a day theme". While there are absolutely no technical details there or mention of tools to achieve that,
I enjoyed it more the second time, since I had the opportunity to ponder the teachings moreso than the tale this time.
I think this book is essential reading currently as it pertains to the state of
As a novel, it's clear the author is well-written but not a fiction writer by trade. I have some qualms about certain characterizations needed to make characters noble or villainous, and the over-reliance on deference to the military. There are reasons these are involved to keep the book moving, but for a book that's a parable it allows too much reading into these aspects than were intended.
The basic teachings of the book, the idea of "The Four Ways" of work and how one should be thinking about workflow, are things I'm now starting to notice both in my personal life and in my professional life and I'm starting to see rewarding effects to consciously engaging with them. In some ways I wish I had read the companion "DevOps Handbook" first so that I could have gotten straight to the meat of the book, but fiction stories are good ways for people to get into these kinds of topics without it feeling too textbook and dry.
On one hand it tries to show how inter-departmental cooperation, especially between IT services and between IT and actual business can prove highly valuable and can speed up and stream-line the main business processes and business-supportive projects/processes.
On the other hand for the dramatic purpose, issues that take significant amount of time in real life are shortened to a ridiculous short time-spans and some teams are shown as very slow-movers and not very capable. Some IT departments are shown as especially ... troublesome.
So I understand some of the reactions to the book (I recognized myself in several characters).
In my opinion what this book does very good is to show what exactly DevOps is - improvement in overall organizational thinking and planning, striving to achieve more in smaller steps [remember those many sayings like brick-by-brick-you-get-a-house]. If everyone is working together, if everyone is motivated and aims for the same - success of the core business - everything can be achieved.
All in all very interesting book that tries [in form of a fiction instead of academic or professional-literature way] to give insights to the readers how things can be much easier achieved through DevOps approach. And funny thing is that all the lections presented are applicable everywhere - not just to IT.
Recommended to everyone interested in organizational and planning issues.
Subjects
Language
Original language
Original publication date
Physical description
ISBN
Local notes
Omslagsillustration: eboy
Omslaget viser stiliserede personer omkring en opbygning af computere, hvor en boblede varm væske gemmer sig i midten
Indskannet omslag - N650U - 150 dpi
Similar in this library
Pages
DDC/MDS
813.6 |