View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Example MappingLASR (Lightweight Approach for Software Reviews)Specification by ExampleFailure Mode and Effects Analysis
| Criterion |  Agile Example Mapping |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Specification by Example |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 30-60 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min pro Feature | 2-6 h |
Participantsdifferent | 3-7 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | 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 | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ArchitectureQualityRiskAssessmentLean | AgileRequirementsExamplesBehavior-Driven Development | RiskQualityOperationsRoot cause |