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 |  Domain Modeling Context Map |  Domain Modeling Domain Context Map |  Agile ROAM Board |
|---|---|---|---|---|
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 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 a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 1-3 h | 20-40 min initial, dann laufend |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 3-10 | 3-15 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Context Map, Integration Patterns, Boundary Notes | Domain Context Map, Boundary Notes, Ownership Map | ROAM Board, Owner List |
Tagsno overlap | RiskTrackingStakeholdersGovernance | Domain-Driven DesignBoundariesStrategy | Domain-Driven DesignContextBoundaries | RiskAgileTrackingAlignment |