Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. The Insider News
  4. The most common reasons why software projects fail

The most common reasons why software projects fail

Scheduled Pinned Locked Moved The Insider News
com
5 Posts 4 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    Kent Sharkey
    wrote on last edited by
    #1

    InfoQ[^]:

    Project failure can be defined as one or a combination of cost overruns, late deliveries, poor quality, and/or developing a product that does not get used.

    "Try again. Fail again. Fail better."

    P M 2 Replies Last reply
    0
    • K Kent Sharkey

      InfoQ[^]:

      Project failure can be defined as one or a combination of cost overruns, late deliveries, poor quality, and/or developing a product that does not get used.

      "Try again. Fail again. Fail better."

      P Offline
      P Offline
      Paul M Watt
      wrote on last edited by
      #2

      I thought that was a well organized and thoughtful article. However, I thought it was odd that they started talking about a QSM proprietary Productivity Index (PI), and I thought that's odd. What's QSM? Then I reached the end and saw that both authors work for QSM. So the problems they point out, seem to be accurate. I am skeptical of any of the solutions they suggest.

      1 Reply Last reply
      0
      • K Kent Sharkey

        InfoQ[^]:

        Project failure can be defined as one or a combination of cost overruns, late deliveries, poor quality, and/or developing a product that does not get used.

        "Try again. Fail again. Fail better."

        M Offline
        M Offline
        Marc Clifton
        wrote on last edited by
        #3

        I've rarely encountered the above reasons. The #1 reason why I see projects fail is very simple: unskilled, untrained, inexperienced programmers. Marc

        Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!

        D 1 Reply Last reply
        0
        • M Marc Clifton

          I've rarely encountered the above reasons. The #1 reason why I see projects fail is very simple: unskilled, untrained, inexperienced programmers. Marc

          Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!

          D Offline
          D Offline
          den2k88
          wrote on last edited by
          #4

          Number #2 rivalling the number #1:

          Marc Clifton wrote:

          unskilled, untrained, inexperienced

          managers. You see, if you work in a place where you need to have the ok from the CEO to buy a pack of pens (price < 5€) and she asks you twice if it is really necessary or if you could work without them, well think what is getting software licences, test equipment, building prototypes... We're testing a 500.000 € machine out of thin air. And it won't fail only because our developers are skilled, trained, experienced, hardened and somewhat masochistic.

          Geek code v 3.12 {      GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*      Weapons extension: ma- k++ F+2 X }

          M 1 Reply Last reply
          0
          • D den2k88

            Number #2 rivalling the number #1:

            Marc Clifton wrote:

            unskilled, untrained, inexperienced

            managers. You see, if you work in a place where you need to have the ok from the CEO to buy a pack of pens (price < 5€) and she asks you twice if it is really necessary or if you could work without them, well think what is getting software licences, test equipment, building prototypes... We're testing a 500.000 € machine out of thin air. And it won't fail only because our developers are skilled, trained, experienced, hardened and somewhat masochistic.

            Geek code v 3.12 {      GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- r++>+++ y+++*      Weapons extension: ma- k++ F+2 X }

            M Offline
            M Offline
            Marc Clifton
            wrote on last edited by
            #5

            den2k88 wrote:

            We're testing a 500.000 € machine

            The CEO is right - the pencils for your writing machine are too expensive! ;) Marc

            Imperative to Functional Programming Succinctly Contributors Wanted for Higher Order Programming Project!

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups