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 Competency Questions |  Facilitation Stakeholder Mapping |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 60–90 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 2-8 | 2-8 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |