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 |  Decision Making Three-Point Estimation |  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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-3 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 10-30 min je Item | Ongoing |
Participantsdifferent | 4-10 | 2-4 pro Pitch | 1-8 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Three-Point Estimate, Risk Range, Assumption Notes | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | PlanningDeliveryAutonomy | EstimationUncertaintyForecasting | FlowVisual managementDelivery |