Analysis Paralysis
This project anti-pattern is related to over analyzing the project to achieve perfection and completeness. Upon execution, many new changes encountered usually discards these analysis, turning them into a waste. Sometimes, the over analysis can make the whole team cease from executing the work.
Symptoms and Consequences
Symptoms and Consequences
- Multiple project restarts and much model rework due to personnel changes or changes in project direction.
- Design and implementation issues are continually reintroduced in the analysis phase.
- Cost of analysis exceeded expectation without a predictable end point.
- Analysis no longer involves user interaction. Many of the analysis performed is speculative.
- Increased complexity until it is impossible to build.
Causes
Causes
- Management assumes waterfall progression of phases.
- Management has more confidence in analysis results instead of actual implementation / prototype data.
- Management insists on completing all analysis before implementation begins.
- Management not wanted to take risks.
- Management fears of failure.
Refactor Recipes
Refactor Recipes
- Convince the management they are introducing resources wastage by:
- Gather possible changes that can rapture the existing analysis.
- Use time as currency, then multiply with monetary.
- Build / facilitate management some forms of dashboard to reduce their interaction from the implementation team. Don't worry, getting into such situation is likely:
- management spending too much time with the team, to the point of micromanagement.