# OPS-2: Change Management

Status: not started

Domain:
- 4.0 Operational Procedures

Objective alignment:
- 4.2 Change management

## What You Need To Know

Change management reduces risk when systems are modified.

Change planning should include:
- Purpose
- Scope
- Change type
- Schedule
- Affected systems
- Risk level
- Responsible staff
- Approvals
- Backup
- Rollback plan
- Sandbox testing
- Implementation steps
- Peer review
- End-user acceptance

Change types:
- Standard: low-risk, preapproved, repeatable
- Normal: planned change requiring review and approval
- Emergency: urgent change to fix major risk or outage

## Memory Trick

Use **P-S-R-B-R**:

- **P**urpose
- **S**cope
- **R**isk
- **B**ackup
- **R**ollback

Shortcut:
- **A change without rollback is a bet, not a plan.**

## Exam Clues

- Maintenance windows reduce user impact.
- Change freezes block noncritical changes during sensitive periods.
- Emergency changes may be faster but still need documentation afterward.
- Peer review helps catch mistakes before implementation.