Cadence and meetings

The rhythm of an engagement: what happens daily, weekly, per sprint and monthly.

A one-week sprint: with AI-assisted engineering we plan, build and release every week. Length and days can be adapted per engagement.

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	BA, Tech Lead, product owner, QA	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 customer 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 Lead to customer	Progress, risks, decisions needed, next steps
Steering review	Monthly	Engagement Manager, sponsor, Tech Lead	Outcomes, budget, roadmap and engagement health

Meeting principles

Every meeting has an owner, an agenda and a written outcome
Decisions and actions are recorded in one place the customer can see
If a meeting has no decisions to make, it is shortened or replaced with a written update
Time zones are respected: overlap hours are agreed at kickoff

Working agreements

Who is responsible, accountable, consulted and informed for each key activity.

Working agreements

The entry and exit checks that keep stories small, clear and truly finished.

Governance

What we measure, how we report it, and how the numbers lead to decisions.