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 Cost of Delay |  Product Strategy RICE Scoring |  Delivery Monte Carlo Forecasting |  Engineering Kanban |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. | When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable. | 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. | 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 | High | Medium | High | Medium |
Timedifferent | 90-180 min | 60-90 min | 30-90 min Setup, danach laufend | Ongoing |
Participantsdifferent | 3-8 | 2-10 | 1-8 | 2-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | CoD Table, Prioritization Sequence | RICE Scores, Ranked List, Assumption Log | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | PrioritizationDeliveryEconomicsDecision | PrioritizationScoringRoadmapTradeoffs | ForecastingFlowDelivery | FlowVisual managementDelivery |