Best laid plans

No project is perfect. This project is far from perfect. But...

When we hit problems and delays we work our collective backsides off to try and get back on track. We try and catch back time so that we don't compromise the launch date.

I've been presented with numerous change requests where I've said "No. This will delay the project and it's a change that, whilst it's nice to have, isn't essential for launch. Make this a post launch change."

I guess it's all about the leadership behaviours that we all know and love and the Drive for Results motivator is the one that's driving me right now, and throughout this project. I guess that's why it's all the more depressing when something hits us that we can't control.

We always knew that hardware sourcing was a risk on the project. It shouldn't be a risk but it is. It should be as simple as outlining requirements, placing an order, receiving delivery and setting everything up. It's not that simple. Don't ask me to explain why it's not that simple because I'll start to get politically incorrect, but it's not that simple.

(If you detect some irritation then you're very perceptive.)

So we expected hardware on Jan 18th and we didn't receive it. Our new delivery date was February 28th and once again nothing was delivered.

We have received something now and we're going through the process of ensuring everything is as it should be and is to spec but it's almost two months late.

I've been trying to think of an analogy that demonstrates how out of our control this part of the development is, so here goes.

Imagine you plan to launch a car in one factory on January 18th but an earthquake demolishes the factory on January 15th. It takes time to recover and rebuild and it's something you couldn't have prevented because it was an act of God.

I'm not suggesting that our hardware suppliers and God are related, far from it, but both are seemingly out of (our) control.