Delivery Playbook · Lifecycle
Stage 3: Build with AI
Deliver working software in small, reviewed steps. AI helps; people stay responsible for the result.
Owner: CTO · Last reviewed: · Next review: 28 April 2027
Goal: Deliver working software in small, reviewed increments.
What happens
- Sprint planning and daily sync
- Implementation with AI assistance under review
- Peer review of every change
- Continuous integration with automated tests and scans
- Sprint demo and retrospective
What you receive
- Working increments in a shared environment
- Automated tests
- Updated documentation
- Sprint report
Quality checks
- Peer review of every change, including AI-assisted ones
- Automated tests, static analysis and dependency checks in the pipeline
- Each story meets the definition of done
Approved before we move on
Each story meets the definition of done; the increment is demonstrated to the client.
Who is involved
- Client Sponsor
- Delivery Manager · leads
- UX/UI Designer
- Tech Lead / Architect · leads
- Software Engineers · leads
- QA / Test Automation
- DevOps / Platform
- CTO · leads
- Support & Operations
How a one-week sprint works
How a change moves
- 1
Pick up a ready story
The engineer takes the next story that meets the definition of ready and checks the business context with the client's team if needed.
- 2
Implement with AI assistance
AI tools may draft code and tests under the AI-use policy. The engineer understands every line.
- 3
Test and self-review
Automated tests are written or updated; the engineer reviews their own diff before asking others.
- 4
Peer review
Another engineer reviews. Changes touching architecture, security or data are reviewed by the Tech Lead or the CTO.
- 5
Merge through the pipeline
CI runs tests, static analysis and dependency checks. Failing checks block the merge.
- 6
Demo and release
At the end of the one-week sprint the team shows working software to the client, collects feedback and releases what has passed the gates.
= 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
Related
Lifecycle
Stage 4: Verify
Prove that the software works, is secure and can be released.
Quality & AI
Quality gates
Four gates a change passes between idea and production, and what each one checks.
Quality & AI
AI engineering
How AI supports the whole engineering workflow, who is responsible for what, and the rules that keep it safe.
