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 Fault Tree Analysis |  Agile Example Mapping |  Operations MORT Analysis |
|---|---|---|---|---|
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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 60-90 min pro Feature | 2-6 h | 30-60 min | Mehrere Tage bis Wochen |
Participantsdifferent | 3-6 | 3-8 | 3-7 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Example Map, Acceptance Criteria, Open Questions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskRoot causeSafety | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Root causeSafetySystemicIncident |