TechSoft
Playbook menu: Quality gates

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

Idea / story1Design2Change3Release candidate4ProductionGATE 1Design approved✓ Problem and successmeasures agreed✓ Architecture reviewed✓ Security screeningGATE 2Ready to merge✓ Peer review✓ Automated tests pass✓ Static and dependencychecksGATE 3Ready to release✓ Regression andacceptance tests✓ Open defects triaged✓ Rollback plan✓ Sponsor approvalGATE 4Outcome check✓ Monitoring healthy✓ Issues triaged✓ Result measured vs.baseline
Nothing moves forward until its gate is passed. Gate 4 closes the loop after release.
GateChecksAccountable
1. Design approvedProblem and success measures agreed; architecture reviewed; security screening doneTech Lead, Client
2. Ready to mergePeer review; automated tests pass; static and dependency checksTech Lead
3. Ready to releaseRegression and acceptance tests; open defects triaged; rollback plan; Client Sponsor approvalClient (release), QA (evidence)
4. Outcome checkMonitoring healthy; issues triaged; result measured against baselineDelivery 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.

ControlWhy it matters to you
Version control and traceable changesYou can see who changed what, when and why, and go back if something goes wrong.
Automated testingMistakes are caught in minutes, not discovered by your users.
Code reviewA second pair of human eyes on every change, including AI-assisted ones.
Static analysis and dependency scanningCommon defects and known-vulnerable libraries are flagged before release.
Security review and remediationFindings are triaged, assigned an owner and tracked until closed or consciously accepted.
Acceptance criteriaEveryone agrees up front what “working” means, so acceptance is not an argument.
Release approvalNothing reaches production without a named approver.
Rollback and recovery planningIf a release misbehaves, there is a tested way back.
Production monitoringProblems are seen by us first, with alerts and dashboards.
Decision rights and escalationEveryone knows who decides what, and how a problem moves up quickly.

Related