View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Agile Example Mapping |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 3-12 | 3-7 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Example Map, Acceptance Criteria, Open Questions | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | AlignmentStakeholdersTeam | Behavior-Driven DevelopmentRequirementsExamplesRefinement | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |