Release readiness: should we go live? Decision based on data.
Criteria (gate the release):
1. Quality gates.
- All Sev 1/2 defects resolved.
- Test coverage 75%+.
- All tests pass.
- Security review passed.
2. UAT.
- Business users signed off.
- All UAT scenarios passed.
3. Performance.
- Load test targets met.
- No regressions.
4. Operational.
- Deployment runbook validated.
- Rollback plan tested.
- Monitoring in place.
- Support team ready.
5. Stakeholder approval.
- Project sponsor signs off.
- Business leadership approves.
Process:
Go/no-go meeting — typically 1-2 days before release.
- Review each criterion.
- Assess any gaps.
- Decision: Go / No-go / Defer.
Documentation:
- Release readiness checklist with status.
- Risk acceptance for any unmet criteria.
- Sign-off.
No-go cases:
- Critical defect unresolved.
- Performance not meeting targets.
- Stakeholder withholds approval.
- Compliance concerns unresolved.
Cost of bad call:
- Going when shouldn't = production incidents, customer impact.
- Not going when could = delay; opportunity cost.
Risk-adjusted:
- Higher-risk system (financial, healthcare) = stricter gates.
- Lower-risk system = some flexibility.
Senior QA insight: say no when needed. Painful but right. Released defects cost more than delays.
The senior framing: the release is QA's brand. Bad releases erode trust.