What is Project failure?
Firstly, let's look at what is meant by failure. A project fails when it has not delivered the benefits that justified it being sponsered at its inception. The benefits are usually either a forecast saving or an increased capacity at a specific cost and/or point in time in the future. A project is then often at risk in realising its benefit if it is late or never delivers, if it is more expensive to deliver, or both.
If the project is ill-conceived - that is, the product(s) of the project will not, once delivered, actually be capable of realising the expected benefit - then the project is destined to fail.
If the wrong resources are applied - that is, a project manager does not have the capacity or capability to manage the project of the type or scale, or is not empowered to obtain resources as required - then the project is destined to fail.
If the corporate culture does not integrate with the adopted project management
methodology - that is, the Key Performance Indicators for management do not provide consideration for matrix management of personnel and resourcing is governed only by line management consideration - then the project is destined to fail.
This is disheartening. If organisations were more honest regarding their performance in project delivery and applied their continuous improvement processes of their quality manual to projects (an often excluded scope to their quality certification), this situation may be given its due focus.
To quote the words of NASA following the return of Apollo 13, most projects are 'successful failure(s)'. Apollo 13 was the 1973 mission to the moon where an accident that should have resulted in the loss of craft and crew was rescued from disaster by the valiant effort of the entire mission team to return the three crew home safely. The mission did not achieve any of its original goals. NASA applied this political spin in a vain effort to harbour support for further funding for moon missions. As in most corporate projects, NASA sold the project for what it achieved, rather than it was targeted to achieve.
Studies since the 1960s have shown that even once the systemic causes for project failure are removed, many still fail. That is, even well conceived projects, that are empowered and appropriately resourced, which use a robust project management methodology that aligns with the corporate culture still fail. Why? Mostly because of a lack of project strategy.
What is a Project Strategy?
Project strategy is the design of how the benefits will be realised from the project processes. Just as driving at the speed limit does not necessarily mean safe driving, so too, complying with best practice in running a well framed project does not mean it will achieve the intended benefits.
Projects do not exist in isolation. They operate through and across an organisation, may involve the supply by external parties while the organisation operates in a market with customers or clients with changing needs. Management via the project strategy ensures the project keeps abreast of its context within the organisation and moves as it does. That is, as the organisation changes the project benefits required, the project via project strategy management responds.
Most projects are like the Titanic, large and near impossible to steer a new course fast enough to avoid disaster or at least failure. When a project is formed with a project strategy it is designed to be nimble and responsive to the changing context of the project within the organisation. It is the single most productive project formation task, yet one that is most often skipped in the rush to commence and one that often slips between the cracks of most project methodologies.