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 Acceptance Criteria Workshop | ![]() Systems Thinking CATWOE Analysis | ![]() Agile Specification by Example |
|---|---|---|---|
Purposedifferent | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | 20-40 min pro Story | 45-90 min | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 3-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | Systems thinkingFramingStakeholders | AgileRequirementsExamplesBehavior-Driven Development |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






