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 Planning Poker |  Agile Ideal Days |  Agile Affinity 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | 2-5 min je Item | 15-60 min | 30-90 min |
Participantsdifferent | 3-6 | 3-9 | 2-9 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Relative Estimates, Assumption Notes, Split Candidates | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileRelative sizingTeam | EstimationEffortAgile | EstimationBacklogRelative sizing |