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 RAPID |  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. | In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels. | 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 | 45-90 min | 20-40 min pro Story |
Participantsdifferent | 3-20 Reviewer | 3-6 | 3-12 | 3-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Example Table, Acceptance Tests | RAPID Role Map, Recommendation, Decision Log | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | AgileRequirementsExamplesBehavior-Driven Development | DecisionRolesGovernance | AgileRequirementsRefinementBehavior-Driven Development |