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 CATWOE Analysis |  Architecture Architecture Communication Canvas |  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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Medium | Low |
Timedifferent | 60-90 min pro Feature | 45-90 min | 60-120 min | 30-60 min |
Participantsdifferent | 3-6 | 3-8 | 2-8 | 3-7 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | CATWOE Canvas, Root Definition, Stakeholder Perspectives, Constraints | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Systems thinkingFramingStakeholders | ArchitectureCommunicationStakeholdersCanvas | Behavior-Driven DevelopmentRequirementsExamplesRefinement |