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 RAID Log |  Facilitation Dot 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | 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 | Low | Low | Medium |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 5-20 min | Ongoing |
Participantsdifferent | 4-10 | 1-3 maintaining, briefing for everyone | 3-20 | 2-12 |
Formatdifferent | Workshop | Async | Workshop | Workshop + async |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanFlowWasteDelivery | RiskTrackingStakeholdersGovernance | EstimationEffortRisk | FlowVisual managementDelivery |