Delivery Playbook · Working agreements
Cadence and meetings
The rhythm of an engagement: what happens daily, weekly, per sprint and monthly.
Owner: Delivery Manager · Last reviewed: · Next review: 28 April 2027
| Meeting | When | Who | Purpose |
|---|---|---|---|
| Daily sync | 15 minutes, daily | Delivery team | Progress, blockers and what needs help today |
| Backlog refinement | Mid-week, for the next sprint | Designer, Tech Lead, engineers, QA, product owner | Clarify upcoming stories and acceptance criteria |
| Sprint planning | Monday (start of each one-week sprint) | Whole team and product owner | Commit to a sprint goal and scope |
| Sprint review / demo and release | Friday (end of each sprint) | Team and client stakeholders | Show working software and collect feedback |
| Retrospective | Friday (end of each sprint) | Delivery team | Improve how we work, including how we use AI |
| Status report | Weekly, with the sprint review | Delivery Manager to client | Progress, risks, decisions needed, next steps |
| Steering review | Monthly | Delivery Manager, Client Sponsor, Tech Lead, CTO | Outcomes, budget, roadmap and engagement health |
Meeting principles
- Every meeting has an owner, an agenda and a written outcome
- We record decisions and actions in one place the client can see
- If a meeting has no decisions to make, we shorten it or replace it with a written update
- We respect time zones and agree overlap hours at kickoff
Related
Working agreements
Decision rights (RACI)
Who is responsible, accountable, consulted and informed for each key activity.
Working agreements
Definition of ready and done
The checks at the start and end of a story that keep stories small, clear and truly finished.
Governance
Metrics and reporting
What we measure across delivery, quality, AI and business outcomes, how we report it, and how the numbers lead to decisions.
