View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile ROAM Board |  Domain Modeling Context Map |  Facilitation Alignment Mapping |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | 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 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20-40 min initial, dann laufend | 1-3 h | 1-2 h | 30 min Setup, dann laufend |
Participantsdifferent | 3-15 | 2-8 | 4-12 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | ROAM Board, Owner List | Context Map, Integration Patterns, Boundary Notes | Alignment Map, Open Issues, Decision Questions | RAID Log, Status Report Source |
Tagsno overlap | RiskAgileTrackingAlignment | Domain-Driven DesignBoundariesStrategy | AlignmentStakeholdersStrategyFacilitation | RiskTrackingStakeholdersGovernance |