View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Agile Example Mapping |  Agile ROAM Board |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | 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 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 | Low | Medium |
Timedifferent | 60-90 min | 30-60 min | 20-40 min initial, dann laufend | 60-90 min pro Feature |
Participantsdifferent | 4-12 | 3-7 | 3-15 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Example Map, Acceptance Criteria, Open Questions | ROAM Board, Owner List | Example Table, Acceptance Tests |
Tagsno overlap | RiskArchitectureWorkshopValidation | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskAgileTrackingAlignment | AgileRequirementsExamplesBehavior-Driven Development |