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 Story Points |  Agile Example Mapping |  Agile Specification by Example |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | When teams want to rate complexity rather than hours, it creates a shared, relative scale. It sorts work by value, risk, and delivery ability. The result is captured as Point Estimates, Reference Stories, and Velocity Data. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | laufend, 1-5 min je Item | 30-60 min | 60-90 min pro Feature | 2-5 min je Item |
Participantsdifferent | 3-9 | 3-7 | 3-6 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Point Estimates, Reference Stories, Velocity Data | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationAgileMeasurement | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileRelative sizingTeam |