ChangeManagement
Formal process for approving/rolling out production changes — change advisory boards, freeze windows.
Why we need this / what value this brings
Uncoordinated production changes are a common cause of avoidable incidents, especially around freezes/releases.
When to use this
Once there's more than one person deploying, or a coordinated release (like a merge freeze) needs to be respected.
How to use or implement this
A simple shared calendar/doc noting freeze windows and who's deploying is enough before a formal CAB process is justified.
Research questions
- Purely enterprise-scale for now, but the 'merge freeze' pattern already showed up once (see project memory) — worth knowing the formal version.
Empty folder — drop notes, links, and findings here as you research.