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 |  Systems Thinking Soft Systems Methodology |  Systems Thinking CATWOE Analysis |  Agile Example Mapping |
|---|---|---|---|---|
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. | Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action. | 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 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. |
Complexitydifferent | Medium | High | Medium | Low |
Timedifferent | 60-90 min pro Feature | 0.5-3 Tage | 45-90 min | 30-60 min |
Participantsdifferent | 3-6 | 5-15 | 3-8 | 3-7 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Rich Picture, Root Definitions, Conceptual Models, Change Agenda | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Soft systemsComplexitySensemakingSystems thinking | Systems thinkingFramingStakeholders | Behavior-Driven DevelopmentRequirementsExamplesRefinement |