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 Example Mapping |  Systems Thinking CATWOE Analysis |  Agile Specification by Example |  Agile Three Amigos |
|---|---|---|---|---|
Purposedifferent | 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. | CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-60 min | 45-90 min | 60-90 min pro Feature | 15-30 min |
Participantsdifferent | 3-7 | 3-8 | 3-6 | 3 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Example Map, Acceptance Criteria, Open Questions | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Example Table, Acceptance Tests | Clarified Story, Test Examples, Open Questions |
Tagsno overlap | Behavior-Driven DevelopmentRequirementsExamplesRefinement | Systems thinkingFramingStakeholders | AgileRequirementsExamplesBehavior-Driven Development | CollaborationBehavior-Driven DevelopmentQualityRefinement |