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 Working Agreements |  Agile ROAM Board |  Knowledge Modeling Concept Mapping |  Knowledge Modeling Knowledge Mapping |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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. | 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. | 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 20-40 min initial, dann laufend | 1-2 h | 1-3 h |
Participantsdifferent | 3-12 | 3-15 | 1-8 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | ROAM Board, Owner List | Concept Map, Relationship Labels, Knowledge Gaps | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | TeamCollaborationAgile | RiskAgileTrackingAlignment | KnowledgeConceptsMappingSensemaking | KnowledgeMappingRisk |