OPS05-BP09 Make frequent, small, reversible changes
Frequent, small, and reversible changes reduce the scope and impact of a change. When used in conjunction with change management systems, configuration management systems, and build and delivery systems frequent, small, and reversible changes reduce the scope and impact of a change. This results in more effective troubleshooting and faster remediation with the option to roll back changes.
Common anti-patterns:
-
You deploy a new version of your application quarterly with a change window that means a core service is turned off.
-
You frequently make changes to your database schema without tracking changes in your management systems.
-
You perform manual in-place updates, overwriting existing installations and configurations, and have no clear roll-back plan.
Benefits of establishing this best practice: Development efforts are faster by deploying small changes frequently. When the changes are small, it is much easier to identify if they have unintended consequences, and they are easier to reverse. When the changes are reversible, there is less risk to implementing the change, as recovery is simplified. The change process has a reduced risk and the impact of a failed change is reduced.
Level of risk exposed if this best practice is not established: Low
Implementation guidance
Use frequent, small, and reversible changes to reduce the scope and impact of a change. This eases troubleshooting, helps with faster remediation, and provides the option to roll back a change. It also increases the rate at which you can deliver value to the business.
Resources
Related best practices:
Related documents:
