Delivery Playbook · Lifecycle
Stage 4: Verify
Prove that the software works, is secure and can be released.
Goal: Prove the software works, is secure and can be released.
Activities
- Regression, integration, performance and exploratory testing
- Security and dependency checks
- User acceptance testing with the customer
- Release readiness review
Artifacts
- Test report and open-defect list
- Security findings and decisions
- Acceptance sign-off
- Release notes and rollback plan
Exit criteria
Release gates passed; customer sponsor approves the release.
Who is involved
- Customer Sponsor
- Engagement Manager
- Delivery Lead
- Business Analyst
- UX/UI Designer
- Tech Lead / Architect
- Software Engineers
- QA / Test Automation · leads
- DevOps / Platform
- Security & Compliance · leads
- AI / Data Engineer
- 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 | Security |
| 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 Lead |
Related
Lifecycle
Stage 5: Operate
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, security and operations roles
QA / Test Automation, DevOps / Platform, Security & Compliance, and Support & Operations.