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 Specification by Example |  Agile Example Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
Purposedifferent | 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 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 60-90 min pro Feature | 30-60 min | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-6 | 3-7 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
