Try Blinkist to get the key ideas from 7,500+ bestselling nonfiction titles and podcasts. Listen or read in just 15 minutes.
Start your free trialBlink 3 of 8 - The 5 AM Club
by Robin Sharma
A Novel about IT, DevOps, and Helping Your Business Win
The Phoenix Project by Gene Kim, Kevin Behr and George Spafford is a business novel that chronicles Bill, an IT manager's journey to revamp his struggling company's processes, using principles of DevOps. It highlights the importance of collaboration, communication and continuous improvement.
It’s Tuesday morning, and Bill is running late for work. He’s speeding down the highway when he gets the call – he’s supposed to come see the CEO, Steve, as soon as he arrives.
Uh-oh, he thinks. I’m going to get fired. It wouldn’t be a huge surprise. As head of a midrange technology group at Parts Unlimited, Bill has always taken pride in doing his job well. He’s built a reputation for being reliable, efficient, and candid; he was a former Marine, after all. But Parts has been struggling, big-time.
Bill looks around the near-empty parking lot he’s pulling into. It seems like its competitors are constantly innovating, and Parts is being left in a trail of dust. With all the layoffs in the past couple years, Bill’s department has increasingly had to do more with fewer resources.
But Steve isn’t firing him. He’s giving Bill a “promotion.” As the new VP of IT Operations, Bill will report directly to Steve and ensure that the impending Phoenix Project rollout is a success. The company’s future depends on Phoenix, Steve says – Bill knows that, right? Customers need to be able to shop from Parts both online and in brick-and-mortar stores. Otherwise, soon there won’t be any customers: the company will no longer exist.
The key message here is: Chaos in the IT department spells failure for the entire company.
Bill doesn’t want the promotion – he’d effectively be agreeing to take on the role of janitor, in charge of cleaning up a colossal IT plumbing mess. So he’s horrified to find himself shaking Steve’s hand in agreement.
Where’s he supposed to start? The entire IT infrastructure is in complete and utter disarray.
John from the Information Security department is continually creating SEV1 outages – critical incidents that everyone has to scramble to fix – because he bypasses the proper clearance procedures to push through Development changes he deems important for auditors. Of course, Operations isn’t ever able to test these changes first; there’s no test environment because there’s no budget.
Meanwhile, Patty, the director of IT Service Support, informs Bill that changes aren’t ever documented; no one wants to spend time using the company’s clunky change management tools. And no one attends the weekly Change Advisory Board, or CAB, meetings.
How does anyone keep track of anything that’s going on? The answer, Bill realizes, is: they don’t. No wonder things have gone to shit.
Bill looks at his desk. His old laptop was displaying the blue screen of death, so he’s just received a replacement. It’s at least ten years old – a bulky, heavy dinosaur of a machine. Half the lettering has worn off, and the battery is taped on.
He can’t help but wonder if the universe is telling him something.
The Phoenix Project (2013) explores how integrating the Development and IT Operations teams of a company’s IT department can improve communication, accelerate workflow, and increase value. It uses a fictional lens to unpack a common real-life scenario – demonstrating how the DevOps approach enables organizations to deftly adapt to sudden changes, updates, or market pressures.
The Phoenix Project (2013) is a compelling narrative that explores the world of IT and its challenges within a fictional organization. Here's why this book is worth reading:
It's highly addictive to get core insights on personally relevant topics without repetition or triviality. Added to that the apps ability to suggest kindred interests opens up a foundation of knowledge.
Great app. Good selection of book summaries you can read or listen to while commuting. Instead of scrolling through your social media news feed, this is a much better way to spend your spare time in my opinion.
Life changing. The concept of being able to grasp a book's main point in such a short time truly opens multiple opportunities to grow every area of your life at a faster rate.
Great app. Addicting. Perfect for wait times, morning coffee, evening before bed. Extremely well written, thorough, easy to use.
Try Blinkist to get the key ideas from 7,500+ bestselling nonfiction titles and podcasts. Listen or read in just 15 minutes.
Start your free trialBlink 3 of 8 - The 5 AM Club
by Robin Sharma
What is the main message of The Phoenix Project?
The main message of The Phoenix Project is the importance of DevOps in transforming IT organizations.
How long does it take to read The Phoenix Project?
The reading time for The Phoenix Project varies, but it typically takes several hours. The Blinkist summary can be read in approximately 15 minutes.
Is The Phoenix Project a good book? Is it worth reading?
The Phoenix Project is a must-read for anyone in the IT industry. It provides valuable insights into improving efficiency and overcoming common challenges.
Who is the author of The Phoenix Project?
The authors of The Phoenix Project are Gene Kim, Kevin Behr, and George Spafford.