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 Knowledge Mapping |  Delivery RAID Log |  Knowledge Modeling Concept Mapping |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 20-40 min pro Story | 1-3 h | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 3-6 | 3-12 | 1-3 maintaining, briefing for everyone | 1-8 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Acceptance Criteria, Story Update | Knowledge Map, Critical Knowledge Areas, Transfer Plan | RAID Log, Status Report Source | Concept Map, Relationship Labels, Knowledge Gaps |
Tagsno overlap | AgileRequirementsRefinementBehavior-Driven Development | KnowledgeMappingRisk | RiskTrackingStakeholdersGovernance | KnowledgeConceptsMappingSensemaking |