Compare

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 Fishbone Diagram	Operations Failure Mode and Effects 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 problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.	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.
Complexitydifferent	Medium	High	Low	High
Timedifferent	60-90 min pro Feature	2-6 h	30-60 min	2-6 h
Participantsdifferent	3-6	3-8	2-8	3-10
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Example Table, Acceptance Tests	Fault Tree, Critical Paths, Cause Hypotheses, Control Actions	Fishbone Diagram, Cause Categories, Investigation Backlog	FMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap	AgileRequirementsExamplesBehavior-Driven Development	RiskRoot causeSafety	Root causeQualityOperations	RiskQualityOperationsRoot cause