At some point, diminishing returns on software investments must trigger a rewrite, Right?
The most often cited reason for businesses to begin entertaining a rewrite or refactor of an application is the crippling speed of further development to meet the businesses’ changing needs.
Moving to refactor or rewrite an application is a big decision that involves:
- Developing a sound business case
- Developing a sound strategy, approach, and work plans
- Understanding the risks to manage
During a refactor, most changes happen “under the hood”, so getting stakeholders to engage becomes a challenge. During a rewrite (or a replace), the main challenge is that the existing application must be kept running until the new one is ready.