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 Ideal Days |  Agile T-Shirt Sizing |  Delivery RAID Log |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | 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 effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 15-60 min | 15-45 min | 30 min Setup, dann laufend | 2-5 min je Item |
Participantsdifferent | 2-9 | 2-12 | 1-3 maintaining, briefing for everyone | 3-9 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Size Buckets, Rough Backlog Map, Split Candidates | RAID Log, Status Report Source | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationEffortAgile | EstimationAgileRoadmap | RiskTrackingStakeholdersGovernance | EstimationAgileRelative sizingTeam |