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 Planning Poker |  Agile Three Amigos |  Agile Specification by Example |  Agile Affinity Estimation |
|---|---|---|---|---|
Purposedifferent | 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | 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 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 | Low | Low | Medium | Medium |
Timedifferent | 2-5 min je Item | 15-30 min | 60-90 min pro Feature | 30-90 min |
Participantsdifferent | 3-9 | 3 | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Clarified Story, Test Examples, Open Questions | Example Table, Acceptance Tests | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | EstimationAgileRelative sizingTeam | CollaborationBehavior-Driven DevelopmentQualityRefinement | AgileRequirementsExamplesBehavior-Driven Development | EstimationBacklogRelative sizing |