Just How Much Do Failed IT Projects Cost?
The statistics for project outcomes depend on whose results you read - the Standish Group conducts their Chaos Survey every two years and they show project failures to be around one quarter of the projects in their sample. The BCS published a study showing 23% of the projects they examined were cancelled.
In their calculations Kim and Orzen take a conservative 20% failure figure, and provide the following start for their calculations:
For just the Standard & Poor 500 companies, aggregate 2012 revenue is estimated to be $10 trillion. If 5 percent of aggregate revenue is spent on IT, and conservatively, 20 percent of that spending creates no value for the end customer - that is $100 billion of waste!
They continue to examine where IT money is spent and say
If we conservatively estimate that 50 percent of global IT spend is on "operate/maintain" activities, and that at least 35 percent of that work is urgent, unplanned work or rework, that's $980 billion worldwide of waste!
They conclude with a call to better management and less waste:
What reward can we expect through better management, operational excellence and governance of IT? If we halve the amount of waste, and instead convert it into 5x of value, that would be (50 percent * $1.2 trillion waste * 5x). That's $3 trillion of potential value that we're letting slip through our fingers!
The analysis can be found here.
Not a very coherent article Shane
However, there is always a lot of 'over-defensive' backlash by IT when the words 'IT project failures' are uttered. Dare I say, this is especially true in the agile community, since we have nobody to blame but ourselves, given that we have spent a lot of time and carried a lot of risk trying to get companies to 'trust us'. Unfortunately, in my experience, the technical critics, especially from solely an agile background, often don't understand enough about business value, accounting nor optimisation to create an adequate critique of the effect of lost projects. Especially in corporate finance and economic terms.
One of the things they routinely forget for example, is that when people are on a project that is failing, those staff are also NOT on a project that is succeeding and delivering value (and income). For companies with only one or two core products or services, this is a catastrophe. You are paying staff to deliver next to no business value and also not making income at the other end to stem that loss. This is not just the loss of an opportunity cost (assuming the business value is not specified adequately at the beginning ;-) it also has a very real component if/when funds are diverted from the successful projects to shore up or pay for the failing projects (fixed costs such as ongoing staff salaries, capital costs, rental space for the team, overheads etc.). This is an example of what is meant by a 'cash flow' problem :-)
I hope to find time to read the critique and return to this.
Re: Not a very coherent article Shane
Thanks for the critical look at the news item.
I realised after reading your comment that I'd left two very important links out of the piece - the link to who Michael is and the link to the published analysis. They are both now in the item above.
Mike Amundsen May 29, 2015
Ben Linders May 28, 2015