The people closest to a problem usually know the most about the problems. This is especially true as the system is complex and dynamic. This means that the further away the person being asked for approval is from the problem, the greater the risk of failure.
Change advisory committees are important, but they should not evaluate every change. Because it is not possible to reliably predict whether a change will succeed simply by reading the description of the change or by validating a checklist.
It is best to rely on peer reviews.
- Pattern #1: Promote a step-by-step migration by using the Strangler application model
- Pattern #2: Testing dependencies
- Pattern #3: Single or multi-repository pattern
- Pattern #4: Data migration
- Pattern #5: Have the changes approved by people close to the problems
More articles on my blog http://www.DevOpsTestLab.com.
My LinkedIn profile: https://fr.linkedin.com/in/brunodelb