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