14 reasons why software projects fail

From outsized expectations to fundamental feature changes, software development projects get derailed — or declared failures — thanks to a variety of project management and technical factors.

14 reasons why software projects fail
Thinkstock

Every software project begins with big dreams and grand visions. Somewhere in an alternative universe, there is a project that fulfills every dream but all too often software projects in our universe stumble toward the finish line and sometimes cross it.  

Analysts might like to toss out random numbers to estimate what percentage of software projects fail, but these are wildly inaccurate by definition because, well, failure is not a binary thing. You can end up with code that runs well but no one uses. Or you can end up with code that won’t even compile. Sometimes you can salvage something useful from the flaming wreckage and sometimes it’s best to run away before it explodes.

When the smoldering mess cools, the autopsies begin and people begin to look for an explanation of what went wrong. Here is a list of the most common reasons software projects fail.

Too few team members

To continue reading this article register now

Survey says! Share your insights in our 19th annual State of the CIO study