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:
“For the child whose impulsiveness is indulged, who retains his primitive-discharge mechanisms, is not only an ill-behaved child but a child whose intellectual development is slowed down. No matter how well he is endowed intellectually, if direct action and immediate gratification are the guiding principles of his behavior, there will be less incentive to develop the higher mental processes, to reason, to employ the imagination creatively. . . .”
—Selma H. Fraiberg (20th century)