View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Agile Ideal Days |  Agile NoEstimates |  Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 15-60 min | laufend | 5-20 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-9 | 2-12 | 3-20 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Throughput Data, Flow Forecast, Slicing Rules | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | RiskTrackingStakeholdersGovernance | EstimationEffortAgile | EstimationForecastingFlow | EstimationEffortRisk |