A standard change is a commonly implemented infrastructure modification with predictable behavior, an established delivery approach, and a defined rollback plan. Its repeatability makes it a candidate for continuous deployment rather than repeated manual approval. section 7.1.4
Treat a change as standard when it has:
- A routine, well-understood implementation that automation can test consistently. section 7.1.4
- A reliable runbook for correcting failure or rolling back without impact. section 7.1.4
- A delivery pipeline that can identify the change and bypass manual production approval. section 7.1.4
Infrastructure examples
Upgrading container images in an orchestrator, deploying a new queue, adding a monitoring alert, or adding servers to a scaling group can be standard changes when their behavior and rollback are established. section 7.1.4
