Iterative replacement
If your existing codebase or technology stack is too out of date, iterative replacement may be the strategy to pivot towards.
If your app is absolutely critical to your business operations and you cannot function without it, you can develop replacement software, increasing the likelihood that your processes remain intact.
For example, we use iterative development as per Government Digital Service principles to progress through discovery, alpha, beta and live phases.
Our developers define the components that need to be replaced, look at the product strategy and roadmaps, and then determine which components are required for your app’s future use.
With defined components and assessed replacements in place, we assess the app’s architecture to ensure it properly fulfills user needs. At this stage, we can replace components iteratively so that disruption and cost are balanced, moving your users over to the replacement, live software. There may be legacy parts of your software that you no longer need or are no longer being used, in which case we can fully retire these components.
This method can take time to ensure the switchover goes smoothly, and there is a possibility of older and newer systems running in parallel – but if the app is critical to ensure your operational success, it’s important to stick with the roadmap and iteratively replace legacy software.
