View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Specification by Example |  Operations MORT Analysis |  Agile Example Mapping |  Operations 5 Whys |
|---|---|---|---|---|
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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 60-90 min pro Feature | Mehrere Tage bis Wochen | 30-60 min | 15-30 min |
Participantsdifferent | 3-6 | 2-6 | 3-7 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Example Table, Acceptance Tests | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Example Map, Acceptance Criteria, Open Questions | Root cause notes, Countermeasures |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Root causeSafetySystemicIncident | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeIncidentLeanProblem solving |