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 Bounded Context Canvas |  Delivery RAID Log |  Domain Modeling Context Map |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. | 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 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. | 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 | Medium | Low |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 1-3 h | 20-40 min initial, dann laufend |
Participantsdifferent | 3-8 | 1-3 maintaining, briefing for everyone | 2-8 | 3-15 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | RAID Log, Status Report Source | Context Map, Integration Patterns, Boundary Notes | ROAM Board, Owner List |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | RiskTrackingStakeholdersGovernance | Domain-Driven DesignBoundariesStrategy | RiskAgileTrackingAlignment |