View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Agile ROAM Board | ![]() Knowledge Modeling NeOn Methodology |
|---|---|---|---|
Purposedifferent | 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. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Low | Low | High |
Timedifferent | 30 min Setup, dann laufend | 20-40 min initial, dann laufend | Mehrere Wochen bis Monate |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-15 | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | ROAM Board, Owner List | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment | OntologyMethodologyReuseSemanticEngineering |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






