View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team API |  Agile Example Mapping |  Agile Affinity Estimation |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | Half day initial, dann laufend | 30-60 min | 30-90 min | 60-90 min pro Feature |
Participantsdifferent | Ein Team plus Stakeholder | 3-7 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Example Map, Acceptance Criteria, Open Questions | Affinity Size Map, Grouped Estimates, Unclear Items | Example Table, Acceptance Tests |
Tagsno overlap | TeamAlignmentCommunicationService | Behavior-Driven DevelopmentRequirementsExamplesRefinement | EstimationBacklogRelative sizing | AgileRequirementsExamplesBehavior-Driven Development |