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 Change Analysis |  Operations Root Cause 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 deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 45-120 min | 1-4 h |
Participantsdifferent | 3-6 | 2-6 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ChangeRoot causeTroubleshootingComparison | Root causeProblem solvingQualityIncident |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
