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 ROAM Board |  Delivery RAID Log |
|---|---|---|---|---|
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 20-40 min initial, dann laufend | 30 min Setup, dann laufend |
Participantsdifferent | 3-10 (Scrum Team) | 3-12 | 3-15 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Knowledge Map, Critical Knowledge Areas, Transfer Plan | ROAM Board, Owner List | RAID Log, Status Report Source |
Tagsno overlap | AgileIterationCadence | KnowledgeMappingRisk | RiskAgileTrackingAlignment | RiskTrackingStakeholdersGovernance |