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 ROAM Board |  Agile Example Mapping |  Architecture Architecture Communication Canvas |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | 20-40 min initial, dann laufend | 30-60 min | 60-120 min | 60-90 min pro Feature |
Participantsdifferent | 3-15 | 3-7 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | ROAM Board, Owner List | Example Map, Acceptance Criteria, Open Questions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Table, Acceptance Tests |
Tagsno overlap | RiskAgileTrackingAlignment | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureCommunicationStakeholdersCanvas | AgileRequirementsExamplesBehavior-Driven Development |