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 Specification by Example |  Delivery RAID Log |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
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 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-2 h | 60-90 min pro Feature | 30 min Setup, dann laufend | 1-3 h |
Participantsdifferent | 1-8 | 3-6 | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Example Table, Acceptance Tests | RAID Log, Status Report Source | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | AgileRequirementsExamplesBehavior-Driven Development | RiskTrackingStakeholdersGovernance | KnowledgeMappingRisk |