Major Software Development Project Failures?

Discussion in 'Software' started by BrokenArrows, Jan 22, 2005.

  1. BrokenArrows

    BrokenArrows Sergeant

    Hey,

    I have been given a project on Major Software Development Project Failures?
    I have to write up a report on a Project that has failed and how it could have been prevented etc.

    Does anyone know of any High Profile failures that i could research?
    Any help would be apreciated. Thanks.
     
  2. DavidGP

    DavidGP MajorGeeks Forum Administrator - Grand Pooh-Bah Staff Member

  3. BrokenArrows

    BrokenArrows Sergeant

    Ya that one does not seem to have much info.

    Id need something where i could find out what the causes of the failure. Keep suggesting if you have any more.
     
  4. QuickSilver

    QuickSilver Corporal

    Well a place to point your research that has been in the news recently is the British NHS IT project, and the doubt cast over whether or not it will work... although the project is still fairly premature and hasn't yet been a complete catastrophe, you could dig into it... Heres an article from The Register...

    http://www.theregister.co.uk/2004/11/03/bma_warns_nhs/
     
  5. BrokenArrows

    BrokenArrows Sergeant

    Thats interesting but im looking for something that has already failed.
     
  6. Kodo

    Kodo SNATCHSQUATCH

  7. Maxwell

    Maxwell Folgers

    Depends what you call failure. There are a number of catastrophic failures due to software bugs after project delivery and a number are listed here: http://www5.in.tum.de/~huckle/bugse.html I'm familiar with the Ariane failure having worked in that industry but not on the Ariane system.

    If you after information about project that were curtailed before delivery again there are plenty of examples. However, typical project failures include but not limited to:

    1) Inadequate specification.
    2) Mission creep - change (usually uncontrolled) of scope during prokect.
    3) Obsolescent technology - exponential rise and change in technology rendered the product out of date or superceded.
    4) Untested software.
    5) No project reviews.
    6) Poor communicationL within team, with client, with senior management, etc.
    7) New innovative technology.
    8) Unrealistic timescales, poor estimation, lack of budget.
    9) Inappropriate hardware, software, design.
    10) Human error.

    and so on - see http://www.etpint.com/whyfail.htm. Essentially you are looking at all the risks to a project and one or more of them have occurred but not planned for or the cost of mitigation is a significant proportion of the project costs. I could go on at length as I've been indoctrinated with a lot of project and business management theory...
     
  8. g1lgam3sh

    g1lgam3sh MajorGeek

  9. Kodo

    Kodo SNATCHSQUATCH

    Sagem.. please don't cross post.
     

MajorGeeks.Com Menu

Downloads All In One Tweaks \ Android \ Anti-Malware \ Anti-Virus \ Appearance \ Backup \ Browsers \ CD\DVD\Blu-Ray \ Covert Ops \ Drive Utilities \ Drivers \ Graphics \ Internet Tools \ Multimedia \ Networking \ Office Tools \ PC Games \ System Tools \ Mac/Apple/Ipad Downloads

Other News: Top Downloads \ News (Tech) \ Off Base (Other Websites News) \ Way Off Base (Offbeat Stories and Pics)

Social: Facebook \ YouTube \ Twitter \ Tumblr \ Pintrest \ RSS Feeds