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 Specification by Example |  Architecture Architecture Inception Canvas |  Agile Example Mapping |
|---|---|---|---|---|
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 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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | Half day initial, dann laufend | 60-90 min pro Feature | 1-2 h | 30-60 min |
Participantsdifferent | Ein Team plus Stakeholder | 3-6 | 3-8 | 3-7 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Team API Document | Example Table, Acceptance Tests | Inception Canvas, Risks, Goal List, Open Questions | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | TeamAlignmentCommunicationService | AgileRequirementsExamplesBehavior-Driven Development | AlignmentArchitectureCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement |