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 T-Shirt Sizing |  Delivery RAID Log |  Decision Making PERT Estimation |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | 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 | Low | Low | Medium | Low |
Timedifferent | 15-45 min | 30 min Setup, dann laufend | 15-45 min | 20-40 min initial, dann laufend |
Participantsdifferent | 2-12 | 1-3 maintaining, briefing for everyone | 1-8 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Size Buckets, Rough Backlog Map, Split Candidates | RAID Log, Status Report Source | PERT Estimate, Expected Value, Risk Notes | ROAM Board, Owner List |
Tagsno overlap | EstimationAgileRoadmap | RiskTrackingStakeholdersGovernance | EstimationUncertaintyRisk | RiskAgileTrackingAlignment |