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 Specification by Example |  Team Design Team API |  Facilitation Expectation Mapping |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 60-90 min pro Feature | Half day initial, dann laufend | 45-90 min | 60-120 min |
Participantsdifferent | 3-6 | Ein Team plus Stakeholder | 3-12 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Team API Document | Expectation Map, Alignment Notes, Agreements | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | TeamAlignmentCommunicationService | AlignmentStakeholdersTeam | ArchitectureCommunicationStakeholdersCanvas |