Kanban ceremonies → ceremony foundation
Purpose: Map Kanban feedback loops and common rituals to methodology-neutral intent types in Ceremony foundation (methodology-neutral).
Guide · Updated · Source
Canonical Kanban narrative: https://forgesdlc.com/methodology-kanban.html · Kanban Guide for Scrum Teams (when blending) · Kanban University — Kanban Guide
Note: Kanban does not mandate one global meeting set; names and cadence are team and service specific. Below maps typical practices.
Practices / meetings × intent types
| Common practice | Foundation intents (primary → secondary) | Notes |
|---|---|---|
| Replenishment (pull selection) | C2 Commit → C1 Align | What gets pulled next given WIP and policies; may be event-driven or on a rhythm. |
| Stand-up / sync | C3 Sync | Flow, blockers, handoffs—often daily or more frequent for urgent services. |
| Service delivery review | C4 Inspect → C5 Improve | Service performance vs expectations (lead time, throughput, customer). |
| Operations review | C5 Improve → C1 Align | Cross-team or dependency health; may feed portfolio Steer. |
| Delivery planning (if used) | C1 Align → C2 Commit | Horizon planning without necessarily a Sprint boundary. |
| Explicit policies / DoD per column | C6 Assure (embedded) | Quality and readiness as work moves—not only a terminal gate. |
C6 in Kanban is often continuous via policies and Definition of Done per state; formal release may still map to C6 at train or deploy boundaries.
Tracking
Cycle time and queue time need board/tracker data; git shows activity, not waiting or blocked time—https://forgesdlc.com/methodology-kanban.html.
Suggestions (Kanban-specific)
| Practice | Suggestions |
|---|---|
| Replenishment | Make C2 policy-driven: who pulls, from which pool, under what WIP cap. Review aging before pulling new work. |
| Stand-up / sync | Focus on flow and blockers (C3); if work ages without movement, treat as C5 input (policy change). |
| Service delivery review | Bring metrics (lead time, throughput, SLA breaches) for C4; agree one service improvement for C5. |
| Operations review | Use for dependencies and Steer visibility—avoid duplicating team-level C3 unless value is clear. |
| Policies / DoD | Document C6 per column in plain language; re-read when defects escape or rework spikes. |
Crosswalk to other methodologies: Methodology bridge — foundation intents ↔ named ceremonies.