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 Story Points |  Delivery RAID Log |  Facilitation Dot Estimation |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | 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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | laufend, 1-5 min je Item | 30 min Setup, dann laufend | 5-20 min | 20-40 min initial, dann laufend |
Participantsdifferent | 3-9 | 1-3 maintaining, briefing for everyone | 3-20 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | RAID Log, Status Report Source | Effort Heatmap, Risk Signals, Discussion Targets | ROAM Board, Owner List |
Tagsno overlap | EstimationAgileMeasurement | RiskTrackingStakeholdersGovernance | EstimationEffortRisk | RiskAgileTrackingAlignment |