View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleARID (Active Reviews for Intermediate Designs)Test CardAcceptance Criteria Workshop
| Criterion |  Agile Specification by Example |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Test Card |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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. | 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. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | 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 | Low | Low |
Timedifferent | 60-90 min pro Feature | 2–4 h review as a planning range; preparation and evaluation additional | 20-35 min | 20-40 min pro Story |
Participantsdifferent | 3-6 | Designers, developers as users, and facilitation | 1-5 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Test Card with a pre-set threshold | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryHypothesis | AgileRequirementsRefinementBehavior-Driven Development |