Release readiness checklist

Pre-release sign-off checklist covering testing, monitoring, rollback, and comms.

360 wordsSign-offPre-releaseChecklist

Release Readiness Checklist — Product Name v0.0

Release version: v0.0 Release date: YYYY-MM-DD Prepared by: Name Reviewed by: Name

Mark each item: ✓ Done | ✗ Not done | N/A Not applicable | ⚠ At risk

#	Item	Owner
T1	All planned test cases executed	QA Lead
T2	Test pass rate meets exit criterion (≥ X%)	QA Lead
T3	0 open Critical defects	QA Lead
T4	0 open High defects (or signed off as acceptable)	QA Lead
T5	Regression suite run on release candidate build	SDET
T6	Regression pass rate meets exit criterion	SDET
T7	Exploratory session(s) completed	QA
T8	UAT completed and signed off by Product Owner	PO
T9	Performance benchmarks within SLA	SDET
T10	Security review / penetration test completed (if required)	Security
T11	Accessibility check completed (if required)	QA / Design

#	Item	Owner
C1	Release branch created and code frozen	Dev Lead
C2	All feature branches merged and PR reviews complete	Dev Lead
C3	No uncommitted changes in release branch	Dev Lead
C4	Build artefact created from release branch	Dev / CI
C5	Build passes all CI checks (lint, type check, unit tests)	CI
C6	Build version number updated correctly	Dev Lead
C7	Changelog / release notes drafted	Dev Lead / PM

#	Item	Owner
E1	Release candidate deployed to staging environment	Dev / Ops
E2	Smoke test passed on staging	QA
E3	Database migrations tested on staging	Dev / DBA
E4	Rollback procedure documented and tested	Dev / Ops
E5	Feature flags / toggles configured correctly for production	Dev
E6	Third-party integrations verified in staging	QA / Dev

#	Item	Owner
M1	Dashboards and alerts reviewed and updated for new features	Ops / SDET
M2	Error rate and latency baselines set for new endpoints	Ops
M3	On-call runbook updated with new failure modes	Ops
M4	Log aggregation confirmed working for new service paths	Ops

#	Item	Owner
COM1	Customer-facing release notes approved by Marketing / Comms	PM / Comms
COM2	Support team briefed on new features and known issues	PM
COM3	Internal stakeholders notified of release schedule	PM
COM4	Go/no-go meeting held and decision documented	PM / QA Lead

Name	Role	Decision
Name	QA Lead	Go / No-go / Hold
Name	Product Owner	Go / No-go / Hold
Name	Dev Lead	Go / No-go / Hold
Name	Engineering Manager	Go / No-go / Hold

Overall decision: Go / No-go / Conditional go

Release version: v3.2.0 Release date: 2024-03-14 Prepared by: Priya Mehta Reviewed by: Ayo Adeyemi

Mark each item: ✓ Done | ✗ Not done | N/A Not applicable | ⚠ At risk

#	Item	Status	Owner	Notes
T1	All planned test cases executed	✓	Priya Mehta	322/322 executed
T2	Test pass rate meets exit criterion (≥ 95%)	✓	Priya Mehta	93.2% — steering group accepted (see TSR-2024-032)
T3	0 open Critical defects	✓	Priya Mehta	0 Critical defects
T4	0 open High defects (or signed off as acceptable)	✓	Priya Mehta	NOVU-2041 and NOVU-2042 verified fixed 2024-03-14 10:30
T5	Regression suite run on release candidate build	✓	Dev Patel	Run against v3.2.0-RC7
T6	Regression pass rate meets exit criterion (≥ 98%)	⚠	Dev Patel	97.6% — 4 tests quarantined (flaky, not feature regressions). Accepted by steering group.
T7	Exploratory sessions completed	✓	Sasha Koval	3 sessions (EXP-2024-045, 046, 047) completed 2024-03-11
T8	UAT completed and signed off by Product Owner	✓	Clara Whitfield	Signed off 2024-03-14 13:45
T9	Performance benchmarks within SLA	✓	Dev Patel	Transfer API: P95 latency 187ms (SLA ≤ 250ms) under 200 concurrent users
T10	Security review completed	✓	Security team	OAuth consent flow reviewed; no vulnerabilities found
T11	Accessibility check completed	N/A	—	Scheduled for v3.3

#	Item	Status	Owner	Notes
C1	Release branch created and code frozen	✓	Ayo Adeyemi	`release/3.2.0` branch created 2024-03-13 17:00
C2	All feature branches merged and PR reviews complete	✓	Ayo Adeyemi	Final PR (NOVU-2042 fix) merged 2024-03-14 09:15
C3	No uncommitted changes in release branch	✓	Ayo Adeyemi	Confirmed clean at 12:00
C4	Build artefact created from release branch	✓	CI	v3.2.0-RC7 built 2024-03-14 09:45
C5	Build passes all CI checks	✓	CI	All checks green on RC7
C6	Build version number updated correctly	✓	Ayo Adeyemi	iOS 3.2.0 (build 320.14), Android versionCode 145
C7	Changelog drafted	✓	Clara Whitfield	Approved by Comms 2024-03-13

#	Item	Status	Owner	Notes
E1	Release candidate deployed to staging	✓	QA Ops	RC7 on staging since 2024-03-14 10:00
E2	Smoke test passed on staging	✓	Sasha Koval	Smoke suite passed 2024-03-14 10:30
E3	Database migrations tested on staging	✓	Dev Patel	Migration v3.2-m001 ran successfully; rollback tested
E4	Rollback procedure documented and tested	✓	Ayo Adeyemi	Runbook updated; rollback to v3.1.3 tested on staging
E5	Feature flags configured correctly for production	✓	Dev	`open_banking_enabled: true`, `biometric_reauth_enabled: true`
E6	Third-party integrations verified in staging	✓	QA	GreenPay, ClearLedger, OpenRoute all verified

#	Item	Status	Owner	Notes
M1	Dashboards updated for new features	✓	QA Ops	Open Banking metrics dashboard live
M2	Error rate and latency baselines set	✓	QA Ops	Baselines set from performance test results
M3	On-call runbook updated	✓	Ayo Adeyemi	Open Banking failure modes added
M4	Log aggregation confirmed	✓	QA Ops	New Open Banking log paths verified in Datadog

#	Item	Status	Owner	Notes
COM1	Customer-facing release notes approved	✓	Clara Whitfield	Approved by Comms 2024-03-13
COM2	Support team briefed	✓	Clara Whitfield	Briefed 2024-03-13; Open Banking FAQ shared
COM3	Internal stakeholders notified	✓	Clara Whitfield	All-hands update 2024-03-11
COM4	Go/no-go meeting held	✓	Priya Mehta	2024-03-14 14:00 UTC — Go decision

Name	Role	Decision	Date
Priya Mehta	QA Lead	Go	2024-03-14
Clara Whitfield	Product Owner	Go	2024-03-14
Ayo Adeyemi	Dev Lead	Go	2024-03-14
James Morley	Engineering Manager	Go	2024-03-14

Overall decision: Go — v3.2.0 released to App Store and Google Play at 16:00 UTC on 2024-03-14.

// Related templates

Test plan

Scope, approach, schedule, risks, entry/exit criteria. IEEE 829-style structure.

Test closure report

Sign-off report when testing completes. Final results, lessons learned, and recommendations.

Risk assessment

Product/release risk register with likelihood, impact, and mitigation per risk.