Delivery Playbook · Quality & AI
Quality gates
Four gates a change passes between idea and production, and what each one checks.
Owner: CTO · Last reviewed: · Next review: 28 April 2027
| Gate | Checks | Accountable |
|---|---|---|
| 1. Design approved | Problem and success measures agreed; architecture reviewed; security screening done | Tech Lead, Client |
| 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; Client Sponsor approval | Client (release), QA (evidence) |
| 4. Outcome check | Monitoring healthy; issues triaged; result measured against baseline | Delivery Manager |
We automate gates wherever we can, so they speed work up instead of slowing it down. Only the accountable role can waive a gate, in writing, with the risk recorded.
The controls behind the gates
These controls make AI-assisted engineering dependable, and each one matters to you. They reduce risk. They do not promise perfect security or zero defects.
| Control | Why it matters to you |
|---|---|
| Version control and traceable changes | You can see who changed what, when and why, and go back if something goes wrong. |
| Automated testing | Mistakes are caught in minutes, not discovered by your users. |
| Code review | A second pair of human eyes on every change, including AI-assisted ones. |
| Static analysis and dependency scanning | Common defects and known-vulnerable libraries are flagged before release. |
| Security review and remediation | Findings are triaged, assigned an owner and tracked until closed or consciously accepted. |
| Acceptance criteria | Everyone agrees up front what “working” means, so acceptance is not an argument. |
| Release approval | Nothing reaches production without a named approver. |
| Rollback and recovery planning | If a release misbehaves, there is a tested way back. |
| Production monitoring | Problems are seen by us first, with alerts and dashboards. |
| Decision rights and escalation | Everyone knows who decides what, and how a problem moves up quickly. |
Related
Lifecycle
Stage 4: Verify
Prove that the software works, is secure and can be released.
Quality & AI
AI engineering
How AI supports the whole engineering workflow, who is responsible for what, and the rules that keep it safe.
Working agreements
Definition of ready and done
The checks at the start and end of a story that keep stories small, clear and truly finished.
