Operations → Deployment
Rollback
The restoration of a previously known-good software or configuration state after a failed change.
What it is
The restoration of a previously known-good software or configuration state after a failed change.
Why it matters
Rollback helps teams reduce ambiguity, coordinate changes, and manage the risk of moving software from source code to users. Its value depends on clear ownership, automation, and feedback rather than the label alone.
Practical guidance
- Define the policy or workflow explicitly.
- Keep changes small, traceable, and reversible.
- Automate repeatable validation where possible.
- Connect decisions to artifacts, environments, releases, and production evidence.
- Review the practice when it creates delay without improving safety.