Analysis Paralysis - Software Development

Software Development

In software development, analysis paralysis typically manifests itself through exceedingly long phases of project planning, requirements gathering, program design and data modeling, with little or no extra value created by those steps. When extended over too long a timeframe, such processes tend to emphasize the organizational (i.e., bureaucratic) aspect of the software project, while detracting from its functional (value-creating) portion.

Analysis paralysis often occurs due to the lack of experience on the part of business systems analysts, project managers or software developers, as well as a rigid and formal organizational culture.

Analysis paralysis is an example of an anti-pattern. Agile software development methodologies explicitly seek to prevent analysis paralysis by promoting an iterative work cycle that emphasizes working products over product specifications.

Read more about this topic:  Analysis Paralysis

Famous quotes containing the word development:

    “The work of adult life is not easy. As in childhood, each step presents not only new tasks of development but requires a letting go of the techniques that worked before. With each passage some magic must be given up, some cherished illusion of safety and comfortably familiar sense of self must be cast off, to allow for the greater expansion of our distinctiveness.”
    —Gail Sheehy (20th century)