SDLC blueprint

Handbook

Kanban — ceremonies (prescriptive)

Kanban **policies** and **cadences** replace fixed Scrum timeboxes. Below: **inputs**, **outputs**, **participants**, **cadence**, **agenda** for the ceremonies most teams need.

Kanban — ceremonies (prescriptive)

Kanban policies and cadences replace fixed Scrum timeboxes. Below: inputs, outputs, participants, cadence, agenda for the ceremonies most teams need.

1. Replenishment (commitment / selection)

Intent: C1 + C2 — decide what moves from options to ready/doing per WIP and policy.
Inputs Ordered options, team capacity/WIP, dependency map, classes of service
Outputs Cards pulled or tagged “next”; updated commitment; transparent queue
Participants SRM/PM (R), delivery team (R), stakeholders (O)
Cadence Weekly or when queue drops below threshold (policy)
Timebox 30–60 min typical

Agenda:

  1. Review aging and blocked work (5 min).
  2. Top of funnel: clarify value and acceptance for candidates (15–25 min).
  3. Pull to match WIP / capacity; agree dates only if policy uses SLA (10–15 min).
  4. Capture policy experiments (5 min).

Meetings: Recurring calendar; shared board view; pre-read for large backlogs.

2. Stand-up / workflow meeting

Intent: C3.
Inputs Board state, blockers, aging highlights
Outputs Unblocks assigned; handoffs clarified; optional swarm decisions
Participants Delivery team (R); SRM (O); coach (O)
Cadence Daily 15 min or 2–3×/week per policy
Format Walk board right-to-left (finish work first)

After stand-up: separate problem-solving huddles.

3. Delivery review (with stakeholders)

Intent: C4 + C6.
Inputs Recently delivered items, metrics (lead time, throughput), demo environment
Outputs Feedback; backlog/options updates; alignment on risk
Participants SRM (R), team (R), stakeholders (R)
Cadence Weekly–monthly per release rhythm

Agenda:

  1. What shipped since last review (10 min).
  2. Demo or walkthrough of increments (20–30 min).
  3. Metrics narrative: flow health, incidents (10–15 min).
  4. Q&A; capture decisions (10 min).

4. Team retrospective

Intent: C5.
Inputs Flow metrics, incidents, qualitative pain, previous actions
Outputs 1–3 experiments (policy/WIP/tooling); owners
Participants Delivery team (R); SRM (O); coach facilitates (O)
Cadence Bi-weekly to monthly

Agenda: same structure as Scrum retro (data → insights → experiments).

5. Service delivery review (SDR)

Intent: C1 + C5 at system level (not just team).
Inputs Cross-team dependencies, portfolio flow, escalation themes
Outputs Management actions; dependency removals; resourcing tweaks
Participants Team reps, service owners, leadership (by invitation policy)
Cadence Monthly–quarterly

Agenda:

  1. Review service-level metrics.
  2. Discuss systemic impediments (policy, HR, tools).
  3. Assign owners outside the team’s control.

6. Quick I/O summary

Ceremony Inputs Outputs
Replenishment Options, WIP Pulled work, clarity
Stand-up Board Unblocks, plan
Delivery review Shipped work Feedback
Retrospective Experience Experiments
SDR System metrics Escalations resolved

Canonical source

Edit https://github.com/autowww/blueprints/blob/main/sdlc/methodologies/kanban/ceremonies-prescriptive.md first; regenerate with docs/build-handbook.py.