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 |  Knowledge Modeling IBIS |  Knowledge Modeling Concept Mapping |  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. | 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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 | Medium |
Timedifferent | 20-40 min pro Story | 1-3 h | 1-2 h | 60-90 min pro Feature |
Participantsdifferent | 3-6 | 2-8 | 1-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Acceptance Criteria, Story Update | Issue Map, Positions, Argument Notes | Concept Map, Relationship Labels, Knowledge Gaps | Example Table, Acceptance Tests |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | RationaleKnowledgeDecision | KnowledgeConceptsMappingSensemaking | AgileRequirementsExamplesBehavior-Driven Development |