View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Acceptance Criteria WorkshopSpecification by ExampleARID (Active Reviews for Intermediate Designs)
| Criterion |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|
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. | 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. | 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 | Low | Medium | Medium |
Timedifferent | 20-40 min pro Story | 60-90 min pro Feature | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 3-6 | 3-6 | Designers, developers as users, and facilitation |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Example Table, Acceptance Tests | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureEngineeringFeedbackValidationTasks |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
