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 man, or the boy, in his development is psychologically deterred from incorporating serving characteristics by an easily observable fact: there are already people around who are clearly meant to serve and they are girls and women. To perform the activities these people are doing is to risk being, and being thought of, and thinking of oneself, as a woman. This has been made a terrifying prospect and has been made to constitute a major threat to masculine identity.”
—Jean Baker Miller (20th century)