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 |  Domain Modeling Context Map |  Delivery Monte Carlo Forecasting |  Decision Making Delphi Method |
|---|---|---|---|---|
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. |
Complexitydifferent | Medium | Medium | High | High |
Timedifferent | Ongoing | 1-3 h | 30-90 min Setup, danach laufend | 1-4 Wochen |
Participantsdifferent | 2-12 | 2-8 | 1-8 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Context Map, Integration Patterns, Boundary Notes | Forecast Percentiles, Throughput Dataset, Risk Communication | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | FlowVisual managementDelivery | Domain-Driven DesignBoundariesStrategy | ForecastingFlowDelivery | ForecastingExpertsDecisionStrategy |