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 |  Agile Ideal Days |
|---|---|---|---|
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 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 | Medium | Low | Low |
Timedifferent | laufend, 1-5 min je Item | 30 min Setup, dann laufend | 15-60 min |
Participantsdifferent | 3-9 | 1-3 maintaining, briefing for everyone | 2-9 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | RAID Log, Status Report Source | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | EstimationAgileMeasurement | RiskTrackingStakeholdersGovernance | EstimationEffortAgile |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
