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 experience of a sense of guilt for wrong-doing is necessary for the development of self-control. The guilt feelings will later serve as a warning signal which the child can produce himself when an impulse to repeat the naughty act comes over him. When the child can produce his on warning signals, independent of the actual presence of the adult, he is on the way to developing a conscience.”
—Selma H. Fraiberg (20th century)