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 ExampleLASR (Lightweight Approach for Software Reviews)Acceptance Criteria WorkshopThree Amigos
| Criterion |  Agile Specification by Example |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Acceptance Criteria Workshop |  Agile Three Amigos |
|---|---|---|---|---|
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. | 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 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 story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 60-90 min pro Feature | 3–4 h for initial assessment; preparation and deeper analysis additional | 20-40 min pro Story | 15-30 min |
Participantsdifferent | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | 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 | Acceptance Criteria, Story Update | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureQualityRiskAssessmentLean | AgileRequirementsRefinementBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement |