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 Example Mapping |  Architecture Risk Storming |  Agile ROAM Board |  Architecture Quality Attribute Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 30-60 min | 60-90 min | 20-40 min initial, dann laufend | 2-4 h |
Participantsdifferent | 3-7 | 4-12 | 3-15 | 5-15 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Annotated Diagram, Prioritized Risk List, Action Backlog | ROAM Board, Owner List | Quality Scenarios, Priority List, Architecture Concerns |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskArchitectureWorkshopValidation | RiskAgileTrackingAlignment | RequirementsArchitectureWorkshop |