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 Example Mapping |  Team Design Team API |  Agile Specification by Example |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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 | Low | Low | Medium | Low |
Timedifferent | 30-60 min | Half day initial, dann laufend | 60-90 min pro Feature | 2-5 min je Item |
Participantsdifferent | 3-7 | Ein Team plus Stakeholder | 3-6 | 3-9 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Team API Document | Example Table, Acceptance Tests | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamAlignmentCommunicationService | AgileRequirementsExamplesBehavior-Driven Development | EstimationAgileRelative sizingTeam |