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)Acceptance Criteria WorkshopLASR (Lightweight Approach for Software Reviews)Specification by Example
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Acceptance Criteria Workshop |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Specification by Example |
|---|---|---|---|---|
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 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 20-40 min pro Story | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min pro Feature |
Participantsdifferent | Designers, developers as users, and facilitation | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Acceptance Criteria, Story Update | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Example Table, Acceptance Tests |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureQualityRiskAssessmentLean | AgileRequirementsExamplesBehavior-Driven Development |