Kanban — major processes & flow maps
Customize column names to your Definition of Workflow.
Guide · Updated · Source
1. Pull through the value stream
Kanban value stream pull
Move work through agreed columns only when downstream capacity can accept it.
- Pull through the value streamFrames the Kanban value stream as governed pull, not push.
- StartWork enters from upstream options or replenishment.
- Core steps (see walkthrough below)Traverse workflow columns under WIP limits and DoD gates.
- OutcomeDelivered value with traceable flow metrics and reviewable Done criteria.
Pull through the value stream
Start
|
v
Core steps (see walkthrough below)
|
v
Outcome
Note: Definition of WorkflowCustomize column names to your Definition of Workflow.
2. Replenishment decision
Replenishment pull decision
Decide which options enter the system when capacity and dependencies allow.
- Replenishment decisionGoverns which backlog options may enter committed flow.
- Current stateAssess queue depth, WIP limits, and class-of-service mix.
- Checkpoint / gateVerify WIP headroom, dependencies, and readiness to pull.
- refine or escalateDefer, split, or run alignment when pull criteria fail.
- Continue flowPull the item into the next column when the gate passes.
Replenishment decision
Current state
|
v
Checkpoint / gate
|
+-- no ──► refine or escalate
|
yes
v
Continue flow3. Blocked work escalation
Blocked work escalation gate
Route blockers to fast team response or formal escalation when policy thresholds hit.
- Blocked work escalationGoverns how blocked cards leave the wait state.
- Current stateCapture blocker type, owner, and time in blocked column.
- Checkpoint / gateCheck whether team policy can resolve the blocker locally.
- refine or escalateEscalate when trade-offs or time limits exceed team authority.
- Continue flowResume pull once the blocker clears or is accepted.
Blocked work escalation
Current state
|
v
Checkpoint / gate
|
+-- no ──► refine or escalate
|
yes
v
Continue flow4. Release train (optional policy)
Release train policy flow
Batch Done work to production on an optional train or calendar cadence.
- Release train (optional policy)Frames how board Done maps to production release.
- StartItems reach Done on the board per DoD.
- Core steps (see walkthrough below)Batch, validate, and deploy per your release train or calendar.
- OutcomeProduction reflects governed releases aligned with board Done.
Release train (optional policy)
Start
|
v
Core steps (see walkthrough below)
|
v
Outcome5. Phase mapping (A–F)
| Phase | Kanban locus |
|---|---|
| A | Options / discovery |
| B | Replenishment |
| C | Doing |
| D | Verify / DoD |
| E | Release policy |
| F | Ops feedback → options |
6. Flow details (walkthrough)
Value stream — Columns are agreed workflow states, governed by your Definition of Workflow and WIP limits. Pull when downstream capacity is available; pushing work into Doing without capacity hides queueing and inflates lead time.
Replenishment — Chooses which options enter the committed system. Items must fit WIP and class-of-service rules and have clear dependencies; otherwise defer, split, or run alignment/spikes before pull.
Escalation — Blockers get fast team response (e.g. swarm) when policy allows. If resolution needs priority trade-offs or misses a time threshold, escalate to service delivery or steering; record the decision before resuming flow.
Release train — Done on the board may still batch to production on a train or calendar. Align the diagram with your release policy (or continuous delivery if that is your Definition of Workflow).
7. Authoritative sources & further reading
- Kanban University — The Kanban Guide — Current guide text for the Kanban method.
- Agile Alliance — Kanban (glossary) — Short definition and roots.
- Kanban Guide for Scrum Teams — Integrating Kanban with Scrum.
- ProKanban.org — Professional Kanban community and training paths.
Full curated list: External reference URLs (methodology guides).