View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Decision Making Assumption Surfacing |  Product Discovery Dual-Track Agile |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as Forecast Percentiles, Throughput Dataset, and Risk Communication. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | Ongoing | 45-90 min | Laufend, Wochen bis Monate | 30-90 min Setup, danach laufend |
Participantsdifferent | 2-12 | 2-8 | 4-10 | 1-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Assumption List, Critical Assumptions, Learning Plan | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | FlowVisual managementDelivery | AssumptionsRiskDecisionDiscovery | AgileDiscoveryDelivery | ForecastingFlowDelivery |