2 ms·
If at all possible, try to find a way to do it incrementally, with options to roll back if things go sideways when something is released. Management rarely wan
by al_borland 2y ago
If at all possible, try to find a way to do it incrementally, with options to roll back if things go sideways when something is released.
Management rarely wants to wait years for before seeing any pay off from a big dramatic cutover, and big sweeping changes are disruptive to clients.
This will likely create more work. Maybe some layer has to be built to allow v1 and v2 subsystems to both operate with the other parts of the app. But it should ultimately make it less stressful.
If you can allow some friendly departments from friendly clients to test and provide feedback before rolling it out to the whole company or the full set of companies, that would probably go a long way to help identify blind spots.
Most importantly, listen to your team and the people who know the systems well. The projects I’ve seen that have really gone sideways are ones where the people who know the true issues are never consulted, or completely ignored when they try to raise an alarm.
- bearjaws 2y ago> try to find a way to do it incrementally, I would make it a hard requirement. If you can't do it incrementally, it's going to fail. Corporations rarely have the attention span and staff tenure to make that kind of migration work. Even if it takes a year of pre-work to get to a point where it can be done incrementally, it will be the only way it gets done.