View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Three-Point Estimation |  Engineering Kanban |  Domain Modeling Context Map |
|---|---|---|---|
Purposedifferent | 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 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 10-30 min je Item | Ongoing | 1-3 h |
Participantsdifferent | 1-8 | 2-12 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Kanban board, WIP policies, Flow metrics | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | EstimationUncertaintyForecasting | FlowVisual managementDelivery | Domain-Driven DesignBoundariesStrategy |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
