TechSoft
Playbook menu: Stage 4: Verify

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

AreaChecksOwner
FunctionalityAcceptance criteria, regression suite, exploratory testingQA
IntegrationAPI contracts, data flows, error handling, third-party systemsQA, Engineers
SecurityDependency scan, secrets scan, access control review, threat model for critical featuresCTO
PerformanceLoad and responsiveness on agreed scenariosQA, DevOps
Usability and accessibilityReview against design; keyboard and contrast checksDesigner, QA
Release readinessRollback plan, monitoring, runbooks, release notesDevOps, Delivery Manager
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.

= milestone agreed with the client

  1. 01

    Discover

    Problem and baseline

  2. 02

    Design

    Architecture and scope

  3. 03

    Build with AI

    Reviewed increments

  4. 04

    Verify

    Gates and acceptance

  5. 05

    Operate & improve

    Monitor and learn

Measure outcomes, learn, and feed the next increment
Each stage ends with a milestone agreed with the client. What we learn in Operate feeds the next round of Discover.

Related