View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Agile NoEstimates |  Delivery Monte Carlo Forecasting |  Decision Making Three-Point Estimation |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Medium |
Timedifferent | 15-45 min | laufend | 30-90 min Setup, danach laufend | 10-30 min je Item |
Participantsdifferent | 1-3 | 2-12 | 1-8 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Throughput Data, Flow Forecast, Slicing Rules | Forecast Percentiles, Throughput Dataset, Risk Communication | Three-Point Estimate, Risk Range, Assumption Notes |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationForecastingFlow | ForecastingFlowDelivery | EstimationUncertaintyForecasting |