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 Three Amigos |  Operations Root Cause Tree Analysis |  Agile Specification by Example |  Operations 5 Whys |
|---|---|---|---|---|
Purposedifferent | When story, test, and implementation could drift apart, it brings business perspective, engineering, and quality together early. It prevents a story from being read differently only late in the process. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-30 min | 1-3 h | 60-90 min pro Feature | 15-30 min |
Participantsdifferent | 3 | 2-8 | 3-6 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Clarified Story, Test Examples, Open Questions | Cause Tree, Evidence Notes, Countermeasures | Example Table, Acceptance Tests | Root cause notes, Countermeasures |
Tagsno overlap | CollaborationBehavior-Driven DevelopmentQualityRefinement | Root causeTreeIncidentQuality | AgileRequirementsExamplesBehavior-Driven Development | Root causeIncidentLeanProblem solving |