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 |  Domain Modeling Domain Context Map |  Systems Thinking Evaporating Cloud |  Agile NoEstimates |
|---|---|---|---|---|
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 a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | When estimating slows a team down more than it helps, it shifts the focus to flow, small slices, and real lead time. It sorts work by value, risk, and delivery ability. The result is captured as Throughput Data, Flow Forecast, and Slicing Rules. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 10-30 min je Item | 1-3 h | 60-120 min | laufend |
Participantsdifferent | 1-8 | 3-10 | 2-8 | 2-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Three-Point Estimate, Risk Range, Assumption Notes | Domain Context Map, Boundary Notes, Ownership Map | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Throughput Data, Flow Forecast, Slicing Rules |
Tagsno overlap | EstimationUncertaintyForecasting | Domain-Driven DesignContextBoundaries | Theory of ConstraintsAssumptionsSystems thinking | EstimationForecastingFlow |