WhatIsFailure agile 15 May 2003
CHAOS report says only 34% of projects succeed.
The Standish Group’s CHAOS report has been talking of billions of wasted dollars on IT projects for many years. The 34% success rate is actually a improvement over 2001’s figure of 28%.
But what do we really mean ‘failure’? The chaos report defines success as on-time, on-budget and with most of the expected features. But is this really success? After all Windows 95 was horribly late yet was extremely successful for Microsoft’s business.
Rather than saying that a project is failed because it is late, or has cost overruns – I would argue that it’s the estimate that failed. So the CHAOS report isn’t chronicling software project failure, it’s chronicling software estimation failure.
So what counts as success? If we could measure it the answer has to be Return on Investment. Sadly this is usually next to impossible to measure. In the end it’s a fuzzy sense of business satisfaction relative to the cost of the project. This may be an unsatisfactorily fuzzy definition, but many business activities are just as fuzzy. Otherwise computers would be CEOs.
Since I’m on a project management kick at the moment, let’s pass along this interesting observation from Martin Fowler. It is certainly popular in IS circles to bemoan the inability to hit project targets. But Fowler makes an important point. The usual assumption is that it is a failure of project management, usually on the part of someone peddling project management tools or someone hoping to take IS down a peg or two.
Fowler is closer to the truth. The superficial resemblance between software development and construction in the physical world obscures the fact that often what we are doing in software development is more R&D than it is general contracting. Knowing which parts of the project are routine and which might be pushing the envelope requires a more sophisticated form of estimating and budgeting than vanilla project management techniques.