Deployment governance
How a code release travels to production: its phases, the evidence each one asks for, two committee authorizations, and an automatic response to a rollback.
The phases
Eleven phases: New, Development, Code Review, Test, To Committee, Committee Authorized, Installed Pre, To Committee Prod, Committee Prod Authorized, Installed Prod, Done.
- Each phase has an owner role and a condition for leaving it.
Evidence at every step
- A pull request link — or a manual change description — before leaving Development.
- An approved code review before testing starts.
- Acceptance test results for QA, pre-production and production.
- Install evidence captured for both pre-production and production.
The committee
Two committee gates, not one: a change is authorized separately for pre-production and for production, each recorded with who gave the authorization and when.
- A workspace-wide committee agenda lists every deployment waiting for a decision.
- Committee minutes gather the decisions of each session.
Rollbacks and compliance
- A production rollback opens a linked bug automatically, at the highest severity, so nothing is lost in the hurry.
- A compliance report compares committed and actual dates for every milestone.