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 Alignment Mapping |  Agile Planning Poker |  Delivery RAID Log |  Agile ROAM Board |
|---|---|---|---|---|
Purposedifferent | 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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 | Low |
Timedifferent | 1-2 h | 2-5 min je Item | 30 min Setup, dann laufend | 20-40 min initial, dann laufend |
Participantsdifferent | 4-12 | 3-9 | 1-3 maintaining, briefing for everyone | 3-15 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Alignment Map, Open Issues, Decision Questions | Relative Estimates, Assumption Notes, Split Candidates | RAID Log, Status Report Source | ROAM Board, Owner List |
Tagsno overlap | AlignmentStakeholdersStrategyFacilitation | EstimationAgileRelative sizingTeam | RiskTrackingStakeholdersGovernance | RiskAgileTrackingAlignment |