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 |  Agile ROAM Board |  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 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. | 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 | Medium |
Timedifferent | 60-90 min pro Feature | 20-40 min initial, dann laufend | 60-120 min |
Participantsdifferent | 3-6 | 3-15 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | ROAM Board, Owner List | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskAgileTrackingAlignment | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
