A lot of IT Operations work is fire-fighting. Things go wrong, the users of the software that’s failed jump up and down and shout, then (hopefully) IT Operations fix the problem and everything goes back to the status quo. The things that go wrong are classified according to their impact on the business. For example a ‘P1’ might be a major failing in the software that allows customers to place orders on the internet – no orders means no profit for the business and this issue would receive the highest priority. In contrast a bug found on a little-used report would receive the lowest priority, perhaps ‘P5’.
The Phoenix Project opens with Bill (who is newly promoted) facing a ‘P1’ issue in the payroll software. He has to find a way of making sure people still get paid and thus avert a labour force walk-out. The stress that Bill is under leaps from the page and, if you’ve ever had to sort out major software problems as part of your job, your heart will increase, you will start sweating and you will empathise fervently with what Bill’s going through.
But the clever thing about The Phoenix Project is that it’s a novel-cum-textbook, so readers learn something too. It is written by three advocates of the DevOps movement (if you’re not in IT don’t worry about that term) and takes the reader on a journey with Bill as he improves the IT landscape for his organisation. It explains the thought processes and practice behind encouraging software developers to work more closely with IT operations colleagues in order to streamline the implementation and testing of new programs.
WARNING: This book should not be taken on holiday or read at bedtime because it will increase not decrease your stress levels.
To 99.9% of you this book will sound deadly boring. But it is a bestseller in its genre. At the time of writing it is #4,052 in the whole UK Paid Kindle Store, out of the four million plus Kindle e-books available. I’m not aware of any marketing for this book – it seems to be all word of mouth from colleague to colleague.
We’re always told to write what we know and to utilise our everyday experiences and working lives. But I’ve always shied away from stories set in computer departments (apart from one Christmas story published by My Weekly last year) because most people would find them tedious. However, The Phoenix Project shows that, with some clever thinking, it is possible to turn the mundane into a successful book.
I wish I’d thought of it first!