This pattern is part of "Patterns of Legacy Displacement"
Start as you mean to continue
Create your legacy replacement in the way you need to continue once it is live.
This page is a stub. We intend to fully expand it in later revisions of this material. However we are still in the middle of developing these patterns, so it's likely that patterns will be renamed, split, or merged as we continue to learn how best to frame and explain these ideas.
When replacing legacy you want to avoid many of the issues you face today, however if you want different outcomes you need to change the organization to get them. This means you need to organize your teams and then build and run your legacy replacement in the manner in which you want to continue. For example to be able to quickly and simply deploy business changes then in our experience it is essential to follow this discipline throughout the development process, even if end-users only see the working software towards the end of the project. It is not realistic to build a systems with one 'big bang' release and then expect to switch to fast and frequent releases after that, if the first release to production environment took a year you should probably expect the next one to take longer.