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 Request for Comments |  Agile Specification by Example |  Decision Making Cynefin Workshop |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | 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. | When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min pro Feature | 60-180 min | 20-40 min pro Story |
Participantsdifferent | 3-20 Reviewer | 3-6 | 4-20 | 3-6 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Example Table, Acceptance Tests | Cynefin Map, Domain-specific Actions, Sensemaking Notes | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | AgileRequirementsExamplesBehavior-Driven Development | ComplexitySensemakingDecision | AgileRequirementsRefinementBehavior-Driven Development |