IT Management - Baseline
Home arrow IT Management arrow What Dooms IT Projects

What Dooms IT Projects

By Dennis McCafferty on 2010-06-10


The failure rate for IT projects, long a concern for both business and technology managers, seems to be on the rise as recession-era budgets pare needed preparation and support. The costs of failed projects, in terms of time, money, opportunity, and morale, can be huge. What causes so many projects to go awry?
  • of
$63 billion is the amount of money spent on IT projects that fail in the U.S.

Only 32 percent of IT projects are considered successful, according to The Standish Group.

Nearly one in four projects are outright failures, up from about one in five before the recession.

Not all projects simply die. Missed deadlines, blown budgets, and end products with inadequate features and functions count, too.

Key Cause of Failure: Lack of User InvolvementUsers must be part of project from beginning to end.

Key Cause of Failure: Unrealistic TimetablesPressure for fast delivery leads to missed deadlines and/or inferior results.

Key Cause of Failure: Poor RequirementsDevelopers struggle when specifications are vague, forcing them to provide what they think is needed.

Key Cause of Failure: Scope creepWhen projects take add requirements on the fly, deadlines and resources often are not properly adjusted accordingly.

Key Cause of Failure:Lack of Executive SupportProject managers need executive muscle problems are encountered.

Key Cause of Failure: Poor TestingInadequately-trained users don't know what to look for; testing objectives must be clear.

  • More slideshows

 
LATEST STORIES

rss graphic
       Baseline Newsletters