Thursday, November 09, 2006

Planning to Fail

When I posted (here and then here) that I was sceptical about the plan to deliver Condor in 6 months, it now appears that I was not the only one. At a meeting earlier this evening, it transpired that I am being instructed to limit our involvement in the project not only to protect the other projects on the portfolio - although there is an element of that in the mix - but also to limit the damage should the project fail.

It was even suggested that the web front-end component should be outsourced to India. This would have two benefits - relieving us of the need to resource it ourselves, and providing someone else to blame when the plan slips.

The fact that The Parent Company is willing to fund and resource a large part of this project means that our part of the company is happy for them to go ahead and get their noses bloodied, while we merrily go on delivering the other planned projects on our workstack.

Why can they not create a realistic and workable plan to succeed, rather than playing political games to limit the damage of failure? Perhaps the fallout from the US mid-term elections has had consequences far beyond the boundaries of the United States, in ways no-one predicted.

This project is starting to get a distinctly nasty smell attached to it.

It is situations like this that make me glad I am publishing these comments anonymously.

No comments: