View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Scrum |  Agile Ideal Days |  Agile Story Points |  Facilitation Dot Estimation |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-60 min | laufend, 1-5 min je Item | 5-20 min |
Participantsdifferent | 3-10 (Scrum Team) | 2-9 | 3-9 | 3-20 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Point Estimates, Reference Stories, Velocity Data | Effort Heatmap, Risk Signals, Discussion Targets |
Tagsno overlap | AgileIterationCadence | EstimationEffortAgile | EstimationAgileMeasurement | EstimationEffortRisk |