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 |  Agile WSJF |  Delivery Monte Carlo Forecasting |  Operations 5 Whys |
|---|---|---|---|---|
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. | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | High | Low |
Timedifferent | Ongoing | 45-90 min | 30-90 min Setup, danach laufend | 15-30 min |
Participantsdifferent | 2-12 | 3-10 | 1-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Ranked Backlog, Cost-of-Delay Assumptions | Forecast Percentiles, Throughput Dataset, Risk Communication | Root cause notes, Countermeasures |
Tagsno overlap | FlowVisual managementDelivery | LeanEconomicsSequencePrioritization | ForecastingFlowDelivery | Root causeIncidentLeanProblem solving |