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 |  Facilitation Dot Estimation |  Agile NoEstimates |  Agile Ideal Days |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 5-20 min | laufend | 15-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-20 | 2-12 | 2-9 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets | Throughput Data, Flow Forecast, Slicing Rules | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | RiskTrackingStakeholdersGovernance | EstimationEffortRisk | EstimationForecastingFlow | EstimationEffortAgile |