Delivery Playbook · Lifecycle
Stage 4: Verify
Prove that the software works, is secure and can be released.
Owner: QA Lead · Last reviewed: · Next review: 28 April 2027
Goal: Prove the software works, is secure and can be released.
What happens
- Regression, integration, performance and exploratory testing
- Security and dependency checks
- User acceptance testing with the client
- Release readiness review
What you receive
- Test report and open-defect list
- Security findings and decisions
- Acceptance sign-off
- Release notes and rollback plan
Quality checks
- Regression, integration and performance testing
- Security and dependency checks; findings triaged
- Rollback plan and release notes ready
Approved before we move on
Release gates passed; the Client Sponsor approves the release.
Who is involved
- Client Sponsor
- Delivery Manager
- UX/UI Designer
- Tech Lead / Architect
- Software Engineers
- QA / Test Automation · leads
- DevOps / Platform
- CTO · leads
- Support & Operations
What we verify
| Area | Checks | Owner |
|---|---|---|
| Functionality | Acceptance criteria, regression suite, exploratory testing | QA |
| Integration | API contracts, data flows, error handling, third-party systems | QA, Engineers |
| Security | Dependency scan, secrets scan, access control review, threat model for critical features | CTO |
| Performance | Load and responsiveness on agreed scenarios | QA, DevOps |
| Usability and accessibility | Review against design; keyboard and contrast checks | Designer, QA |
| Release readiness | Rollback plan, monitoring, runbooks, release notes | DevOps, Delivery Manager |
= milestone agreed with the client
01
Discover
Problem and baseline
02
Design
Architecture and scope
03
Build with AI
Reviewed increments
04
Verify
Gates and acceptance
05
Operate & improve
Monitor and learn
Measure outcomes, learn, and feed the next increment
Related
Lifecycle
Stage 5: Operate and improve
Run, measure and keep improving the software after release.
Quality & AI
Quality gates
Four gates a change passes between idea and production, and what each one checks.
Roles
Quality and operations roles
QA / Test Automation, DevOps / Platform, and Support & Operations. Security and compliance sit with the CTO.
