Delivery Playbook · Quality & AI
Quality gates
Four gates a change passes between idea and production, and what each one checks.
| Gate | Checks | Accountable |
|---|---|---|
| 1. Design approved | Problem and success measures agreed; architecture reviewed; security screening done | Tech Lead, Customer |
| 2. Ready to merge | Peer review; automated tests pass; static and dependency checks | Tech Lead |
| 3. Ready to release | Regression and acceptance tests; open defects triaged; rollback plan; sponsor approval | Customer (release), QA (evidence) |
| 4. Outcome check | Monitoring healthy; issues triaged; result measured against baseline | Engagement Manager |
Gates are automated wherever possible, so they speed work up instead of slowing it down. A gate can only be waived by the accountable role, in writing, with the risk recorded.
Related
Lifecycle
Stage 4: Verify
Prove that the software works, is secure and can be released.
Quality & AI
AI-assisted engineering
Where we use AI, the rules that keep it safe, and who is responsible.
Working agreements
Definition of ready and done
The entry and exit checks that keep stories small, clear and truly finished.