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 Quality Attribute Workshop |  Architecture Request for Comments |  Agile Specification by Example |
|---|---|---|---|---|
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. | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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 | Medium | Medium | Medium |
Timedifferent | 30-60 min | 2-4 h | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min pro Feature |
Participantsdifferent | 3-7 | 5-15 | 3-20 Reviewer | 3-6 |
Formatdifferent | Workshop | Workshop | Async | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | Quality Scenarios, Priority List, Architecture Concerns | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Example Table, Acceptance Tests |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RequirementsArchitectureWorkshop | ArchitectureDecisionAsyncGovernance | AgileRequirementsExamplesBehavior-Driven Development |