Project Mismanagement

This project anti-pattern is mainly due to bad management.

Symptoms and Consequences

• Project is too difficult to implement due to lack of architectural strategy.
• Code reviews and inspections happen infrequently and add minimal value.
• The test design requires extra effort and guesswork because the behavioral guidelines for the system are inadequately defined.
• In the integration and system testing phases, there is much project "thrashing" due to a large number of defects that should have been eliminated in earlier phases such as architecture, design, inspection, and unit testing.
• Defect reports escalate toward the end of the development and delivery/acceptance phases.

Causes

• Inadequate architecture that is absent of technical criteria for inspection, testing, integration, and interoperatbility.
• Code reviews and software inspections do not evaluate design defects.
• Insufficient test suite coverage.
• All preceding factors indicate ineffective risk management.

Refactor Recipes

Managerial

• Re-evaluate end-to-end processes again.
• Re-evaluate roles in the processes to be effective.
• Re-evaluate the aspects to prevent common project failure points:
  • cost overruns.
  • premature termination of project.
  • development of the wrong product.
  • technical failure.

Quality

• Program and project management.
• Project identification.
• Architectural definition.
• Solution design.
• Solution implementation (coding)
• Solution validation (testing)
• Product support

Common Understanding

• find out all the missed functionality and act accordingly.
• find out all the incorrect functionality and act accordingly.
• find out all the over functionality and act accordingly.
• Code modules are not fully inter-operate.