View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 2-8 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
