To that point, I’m wondering if all IT initiatives codenamed “Phoenix” are doomed from the start, given that the implication is “let’s burn down everything we have that works, and rise anew from the ashes”...
Well, one possibility is that I am the common factor in all of my bad relationships. But another possibility is that projects tend to get named 'Phoenix' for a reason, and that just as in real life, it's pretty hard to successfully be reborn from a pile of ashes.
Not just all IT initiatives - I just heard today that the project that would eventually create the Ford Pinto was also named Phoenix. (from Stuff You Should Know podcast)
The Pinto was a good car, though, even with the one design flaw that was actually the result of both best practices for the time and a lack of regulation. Except for that, the Pinto was a landmark subcompact car.
It wasn't a bad book, but if you've read anything by Eli Goldratt on the theory of constraints (The Goal, for example) then Phoenix Project just looks like a watered down, IT-focused, and nearly plagiarized variation.
I can literally do that with my DigitalOcean droplet. I can destroy the instance and run a bash script to provision a new, identical machine in around 3 minutes.
It’s a lot of hard work to get every little detail working automatically. Probably 10x as much as just manually setting things up from scratch. But in the long-term it can pay off.
To that point, I’m wondering if all IT initiatives codenamed “Phoenix” are doomed from the start, given that the implication is “let’s burn down everything we have that works, and rise anew from the ashes”...