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 ExampleFailure Mode and Effects AnalysisGemba WalkLASR (Lightweight Approach for Software Reviews)
| Criterion |  Agile Specification by Example |  Operations Failure Mode and Effects Analysis |  Operations Gemba Walk |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | 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. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | 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. |
Complexitydifferent | Medium | High | Low | Medium |
Timedifferent | 60-90 min pro Feature | 2-6 h | 30-120 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-6 | 3-10 | 2-6 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | FMEA Table, Risk Priority, Mitigation Actions | Observation Notes, Improvement Ideas | 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 |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskQualityOperationsRoot cause | LeanObservationProcessOperations | ArchitectureQualityRiskAssessmentLean |