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 WSJF |  Engineering Kanban |  Product Strategy ICE Scoring |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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 ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list. | 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 | High | Medium | Low | High |
Timedifferent | 45-90 min | Ongoing | 30-60 min | 30-90 min Setup, danach laufend |
Participantsdifferent | 3-10 | 2-12 | 2-8 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Kanban board, WIP policies, Flow metrics | ICE Table, Top Idea List | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | LeanEconomicsSequencePrioritization | FlowVisual managementDelivery | PrioritizationScoringGrowthDecision | ForecastingFlowDelivery |