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 |  Agile Ideal Days |  Delivery Monte Carlo Forecasting |
|---|---|---|---|---|
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. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. |
Complexitydifferent | Low | Medium | Low | High |
Timedifferent | 15-45 min | laufend | 15-60 min | 30-90 min Setup, danach laufend |
Participantsdifferent | 1-3 | 2-12 | 2-9 | 1-8 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Throughput Data, Flow Forecast, Slicing Rules | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Forecast Percentiles, Throughput Dataset, Risk Communication |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | EstimationForecastingFlow | EstimationEffortAgile | ForecastingFlowDelivery |