The Phoenix Project

Let me present this great novel on IT from Gene Kim, Kevin Behr and George Spafford:

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.

Here are some key highlights I found so far:

  • P81 – definition of change: any activity that is physical, logical, or virtual to applications, databases, operating systems, networks, or harware that could impact services being delivered.
  • P89 – concept of the work in progress defined as the silent killer. p113 – too many WIP for Brent. It reminds me the Agile concept around limiting that WIP, which I am starting to do since beg of this year thru the usage of a personal Kanban.
  • P91 – IT Operations roles and the 3 ways
  • P100-102 – objective and scope of the CAB

Laisser un commentaire

Votre adresse de messagerie ne sera pas publiée. Les champs obligatoires sont indiqués avec *