View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleTeam APIArchitecture Communication CanvasArchitecture Inception Canvas
| Criterion |  Agile Specification by Example |  Team Design Team API |  Architecture Architecture Communication Canvas |  Architecture Architecture Inception 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | Half day initial, dann laufend | 60-120 min | 1-2 h |
Participantsdifferent | 3-6 | Ein Team plus Stakeholder | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Team API Document | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Inception Canvas, Risks, Goal List, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | TeamAlignmentCommunicationService | ArchitectureCommunicationStakeholdersCanvas | AlignmentArchitectureCanvas |