Slashdot Mirror

← Back to Stories (view on slashdot.org)

Identifying (and Fixing) Failing IT Projects

Posted by ScuttleMonkey on from the if-it-aint-baroque-don't-fix-it dept.

Esther Schindler writes "Often, the difference between the success and failure of any IT project is spotting critical early warning signs that the project is in trouble. CIO.com offers a few ways to identify the symptoms, as well as suggestions about what you can do to fix a project gone wrong. ' The original study (which is still sometimes quoted as if it were current) was shocking. In 1994, the researchers found that 31 percent of the IT projects were flat failures. That is, they were abandoned before completion and produced nothing useful. Only about 16 percent of all projects were completely successful: delivering applications on time, within budget and with all the originally specified features. "As of 2006, the absolute failure rate is down to 19 percent," Johnson says. "The success rate is up to 35 percent." The remaining 46 percent are what the Standish Group calls "challenged": projects that didn't meet the criteria for total success but delivered a useful product.'"

2 of 144 comments (clear)

  1. Sounds like MY career, anyway... by The_REAL_DZA · · Score: 5, Insightful

    That 31%-flat-failure rate sounds just about right; about a third of the projects I've worked on over the last 15 years have been complete flops (with the usual list of various reasons from "bad idea to begin with so it needed killin' " to "we changed bosses and since your project wasn't the new boss' idea..."), but I'd have to challenge the notion from TFA that they "produced nothing useful", because I've learned something I didn't know and wouldn't have otherwise known from each of them -- in other words, I'd count them all as at least partial successes because I personally gained something from them.

    --


    This space intentionally left (almost) blank.
  2. Re:With Major Hopeful's help by ElectricRook · · Score: 5, Insightful

    One problem I see, is that many IT projects begin with the goal of making the project manager look good.

    The proper way to start a project is: How can we fix BAD THING. Instead of the usual "We should migrate this to SAP cause that would look so cool on my review".

    Many times IT projects become a destination, instead of a method to reach the companies destination be it ( manufacturing / sales / service ).

    --
    - High Tech workers, please say NO to Union Carpenters, their Union sees fit to control our compensation.