TechSoft
Playbook menu: Cadence and meetings

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

MonTueWedThuFriONE-WEEK SPRINTDaily sync (15 min)Backlog refinementPlanning / reviewReleaseStatus reportBuild, test, integrateRefine next weekPlanningReview + retroReleaseWeekly reportReviewed changes merge continuously; checks run on every change
A one-week sprint: with AI-assisted engineering we plan, build and release every week. Length and days can be adapted per engagement.
MeetingWhenWhoPurpose
Daily sync15 minutes, dailyDelivery teamProgress, blockers and what needs help today
Backlog refinementMid-week, for the next sprintDesigner, Tech Lead, engineers, QA, product ownerClarify upcoming stories and acceptance criteria
Sprint planningMonday (start of each one-week sprint)Whole team and product ownerCommit to a sprint goal and scope
Sprint review / demo and releaseFriday (end of each sprint)Team and client stakeholdersShow working software and collect feedback
RetrospectiveFriday (end of each sprint)Delivery teamImprove how we work, including how we use AI
Status reportWeekly, with the sprint reviewDelivery Manager to clientProgress, risks, decisions needed, next steps
Steering reviewMonthlyDelivery Manager, Client Sponsor, Tech Lead, CTOOutcomes, 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