Common Causes of Failure


Having pointed out the similarities between a mountaineering expedition and a software development project, I assert that software projects fail for some of the same reasons climbing expeditions fail. Many of these issues will come up over and over again in later chapters. Let's take the mountaineering "failure modes" and find their software development analogs:

  • Trying to get to the summit too quickly.

    Analog: Unrealistic schedule from the start.

  • Trying to get to the summit with clearly inadequate resources.

    Analog: Not enough good people or tools.

  • Climbing with a team that is too big; the logistical and communications burdens overwhelm the team.

    Analog: Too many mediocre developers in relation to superior developers.

  • Taking too long; teams that stay on the mountain too long lose their verve, energy, and desirefatigue takes its toll. Also, they may simply run out of resources.

    Analog: Software projects that stretch out forever, taking so long that the requirements get changed, sometimes multiple times.

  • Sticking to the wrong route in the face of new information.

    Analog: Ignoring data from early iterations; failure to adjust the plan during the course of the project.

  • Getting wiped out by circumstances beyond the climbers' control.

    Analog: Supplier or subcontractor failure; failure of a key component that was really an R&D activity, not product-ready.

  • Not having a reasonable plan that everyone understands, believes can succeed, and is totally committed to.

    Comment: Usually the result of a top-down, hierarchically mandated plan.

  • Failing to execute, within tolerances, according to the plan.

    Comment: Sometimes results from the accumulation of many small slips, rather than any one spectacular failure.

  • Losing gumption when the going gets tough; not understanding that adversity is part of the endeavor.

    Comment: Just as bad at the office as on the mountain.

  • Not having any reserve for emergencies.

    Comment: Usually the experience of the senior players can provide some of this reserve; they'll know what to do when the unexpected happens.




The Software Development Edge(c) Essays on Managing Successful Projects
The Software Development Edge(c) Essays on Managing Successful Projects
ISBN: N/A
EAN: N/A
Year: 2006
Pages: 269

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net