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 | ![]() Delivery RAID Log | ![]() Agile ROAM Board | ![]() Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
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. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 2-4 h | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | 20-40 min pro Story |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 3-15 | 3-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | RAID Log, Status Report Source | ROAM Board, Owner List | Acceptance Criteria, Story Update |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | AgileRequirementsRefinementBehavior-Driven Development |



