View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Risk StormingSpecification by ExampleLASR (Lightweight Approach for Software Reviews)Example Mapping
| Criterion |  Architecture Risk Storming |  Agile Specification by Example |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Example Mapping |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 60-90 min | 60-90 min pro Feature | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min |
Participantsdifferent | 4-12 | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 3-7 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | RiskArchitectureWorkshopValidation | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureQualityRiskAssessmentLean | Behavior-Driven DevelopmentRequirementsExamplesRefinement |