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 |  Agile Example Mapping |  Knowledge Modeling IBIS |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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. | 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. | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 60-90 min pro Feature | 30-60 min | 1-3 h | 20-40 min pro Story |
Participantsdifferent | 3-6 | 3-7 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Example Table, Acceptance Tests | Example Map, Acceptance Criteria, Open Questions | Issue Map, Positions, Argument Notes | Acceptance Criteria, Story Update |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RationaleKnowledgeDecision | AgileRequirementsRefinementBehavior-Driven Development |