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 Monte Carlo Forecasting |  Engineering Kanban |  Agile Example Mapping |
|---|---|---|---|
Purposedifferent | 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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | High | Medium | Low |
Timedifferent | 30-90 min Setup, danach laufend | Ongoing | 30-60 min |
Participantsdifferent | 1-8 | 2-12 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Forecast Percentiles, Throughput Dataset, Risk Communication | Kanban board, WIP policies, Flow metrics | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ForecastingFlowDelivery | FlowVisual managementDelivery | Behavior-Driven DevelopmentRequirementsExamplesRefinement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
