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 Concept Mapping |  Agile ROAM Board |  Decision Making Red Teaming |
|---|---|---|---|---|
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. | 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 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. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-2 h | 20-40 min initial, dann laufend | 1-4 h |
Participantsdifferent | 3-10 (Scrum Team) | 1-8 | 3-15 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Concept Map, Relationship Labels, Knowledge Gaps | ROAM Board, Owner List | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | AgileIterationCadence | KnowledgeConceptsMappingSensemaking | RiskAgileTrackingAlignment | RiskDecisionSensemaking |