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 |  Facilitation Team Charter |
|---|---|---|---|
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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30-60 min | Half day initial, dann laufend | 2-4 h |
Participantsdifferent | 3-7 | Ein Team plus Stakeholder | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Team API Document | Team Charter, Working Norms, Role Notes |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | TeamAlignmentCommunicationService | TeamAlignmentCollaboration |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
