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 |  Decision Making Three-Point Estimation |  Domain Modeling Context Map |  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. | A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes. | 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. | 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 | Medium | High |
Timedifferent | Ongoing | 10-30 min je Item | 1-3 h | 1-4 Wochen |
Participantsdifferent | 2-12 | 1-8 | 2-8 | 6-30 Experten |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Three-Point Estimate, Risk Range, Assumption Notes | Context Map, Integration Patterns, Boundary Notes | Expert Forecast, Consensus Range, Assumption Notes |
Tagsno overlap | FlowVisual managementDelivery | EstimationUncertaintyForecasting | Domain-Driven DesignBoundariesStrategy | ForecastingExpertsDecisionStrategy |