View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile NoEstimates |  Innovation Lean Startup |  Engineering Kanban |  Delivery Value Stream Mapping |
|---|---|---|---|---|
Purposedifferent | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | laufend | Wochen bis Monate je Lernzyklus | Ongoing | 1-3 h |
Participantsdifferent | 2-12 | 2-8 | 2-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Throughput Data, Flow Forecast, Slicing Rules | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Kanban board, WIP policies, Flow metrics | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | EstimationForecastingFlow | LeanStartupValidationMVP | FlowVisual managementDelivery | LeanFlowWasteDelivery |