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 Planning Poker |  Delivery RAID Log |  Agile Affinity Estimation |
|---|---|---|---|---|
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 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 many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 2-5 min je Item | 30 min Setup, dann laufend | 30-90 min |
Participantsdifferent | 3-12 | 3-9 | 1-3 maintaining, briefing for everyone | 3-12 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Relative Estimates, Assumption Notes, Split Candidates | RAID Log, Status Report Source | Affinity Size Map, Grouped Estimates, Unclear Items |
Tagsno overlap | AlignmentStakeholdersTeam | EstimationAgileRelative sizingTeam | RiskTrackingStakeholdersGovernance | EstimationBacklogRelative sizing |