View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Concept Mapping |  Agile Example Mapping |  Knowledge Modeling IBIS |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | 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 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 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 | Medium | Low | Medium | Medium |
Timedifferent | 1-2 h | 30-60 min | 1-3 h | 60-90 min pro Feature |
Participantsdifferent | 1-8 | 3-7 | 2-8 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Example Map, Acceptance Criteria, Open Questions | Issue Map, Positions, Argument Notes | Example Table, Acceptance Tests |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RationaleKnowledgeDecision | AgileRequirementsExamplesBehavior-Driven Development |