View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Delivery Shape Up | ![]() Architecture Architecture Inception Canvas | ![]() Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-2 h | Ongoing |
Participantsdifferent | 4-10 | 2-4 pro Pitch | 3-8 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Inception Canvas, Risks, Goal List, Open Questions | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | PlanningDeliveryAutonomy | AlignmentArchitectureCanvas | FlowVisual managementDelivery |



