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 T-Shirt Sizing |
|---|---|---|---|
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 effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 15-60 min | 15-45 min |
Participantsdifferent | 3-10 (Scrum Team) | 2-9 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Size Buckets, Rough Backlog Map, Split Candidates |
Tags1 shared | AgileIterationCadence | EstimationEffortAgile | EstimationAgileRoadmap |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
