View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Specification by ExampleRiskiest Assumption Test
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Specification by Example |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|
Purposedifferent | 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. | 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 an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 60-90 min pro Feature | 1-2 Wochen pro Iteration |
Participantsdifferent | Designers, developers as users, and facilitation | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Example Table, Acceptance Tests | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | AgileRequirementsExamplesBehavior-Driven Development | ExperimentsValidationDiscoveryAssumptions |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
