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 |  Operations Barrier Analysis |  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. | For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | 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 | Medium | High |
Timedifferent | 60-90 min pro Feature | 2-6 h | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-6 | 3-8 | 2-6 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | RiskRoot causeSafety | Root causeSafetyIncident | Root causeSafetySystemicIncident |