CIO.com cites a Dynamic Markets survey of 800 IT managers, reporting that 62 percent of IT projects fail to meet their schedules. Other data:
- 49 percent suffered budget overruns
- 47 percent had higher-than-expected maintenance costs, and
- 41 percent failed to deliver the expected business value and ROI
This wouldn't be so bad, CIO.com notes, if it weren't for the fact that the numbers haven't appreciably improved over the past decade. In some cases, they've gotten worse.
Why? Why do 25 percent of all IT projects get canceled before completion? CIO.com cites two reasons:
- IT departments don't take into account the time required between design and development and
- QA is not adequately understood and budgeted into projects' timelines.
One other thing that I've seen fairly often is a disconnect between the IT department and the business owners who sponsor IT projects. The two often have very different ideas as to what they want.
From the business owner side, they are often more enamored of demos than technology. This is sometimes good but also just as often bad. One customer of mine has had its Alfresco implementation delayed by a year because a three-month project with a proprietary product has taken over 15 months. The proprietary software that IT is attempting to deploy looks great in demos, but is a pile of potty to deploy.
Other times, it's the IT department that leads with technology and overlooks business owners' requirements. I've had this early in my company's product lifecycle when it showed great promise but little polish. We had a customer attempt to deploy the product for something it was ill-equipped to do...and the business owner rejected it.
I'm not sure what the solution is for this disconnect, but I suspect it's the cause of more IT project failures than most others. Any suggestions?