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 Scrum |  Knowledge Modeling Knowledge Mapping |  Agile Acceptance Criteria Workshop |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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. | 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. | 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 | Medium | Low | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 20-40 min pro Story | 60-90 min pro Feature |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 3-6 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Acceptance Criteria, Story Update | Example Table, Acceptance Tests |
Tagsno overlap | AgileIterationCadence | KnowledgeMappingRisk | AgileRequirementsRefinementBehavior-Driven Development | AgileRequirementsExamplesBehavior-Driven Development |