View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Fault Tree Analysis |  Agile Example Mapping |  Agile Specification by Example |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | 2-6 h | 30-60 min | 60-90 min pro Feature | 2-4 h |
Participantsdifferent | 3-8 | 3-7 | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Example Map, Acceptance Criteria, Open Questions | Example Table, Acceptance Tests | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | RiskRoot causeSafety | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development | Root causeSafetyIncident |