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 Planning Poker |  Facilitation Expectation Mapping |  Delivery RAID Log |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 2-5 min je Item | 45-90 min | 30 min Setup, dann laufend | 1-2 h |
Participantsdifferent | 3-9 | 3-12 | 1-3 maintaining, briefing for everyone | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Expectation Map, Alignment Notes, Agreements | RAID Log, Status Report Source | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | EstimationAgileRelative sizingTeam | AlignmentStakeholdersTeam | RiskTrackingStakeholdersGovernance | AlignmentStakeholdersStrategyFacilitation |