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