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 Acceptance Criteria Workshop |  Architecture Request for Comments |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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 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 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 | Low | Medium |
Timedifferent | 20-40 min pro Story | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 3-20 Reviewer | 3-7 | 3-6 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureDecisionAsyncGovernance | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |