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 Specification by Example |  Agile T-Shirt Sizing |  Facilitation Dot Estimation |  Decision Making PERT Estimation |
|---|---|---|---|---|
Purposedifferent | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | When effort only needs to be classified roughly, it makes comparability more important than false precision. It helps sort work quickly into manageable sizes. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 15-45 min | 5-20 min | 15-45 min |
Participantsdifferent | 3-6 | 2-12 | 3-20 | 1-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Size Buckets, Rough Backlog Map, Split Candidates | Effort Heatmap, Risk Signals, Discussion Targets | PERT Estimate, Expected Value, Risk Notes |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileRoadmap | EstimationEffortRisk | EstimationUncertaintyRisk |