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 Affinity Estimation |  Delivery RAID Log |  Agile Planning Poker |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 30-90 min | 30 min Setup, dann laufend | 2-5 min je Item |
Participantsdifferent | 3-12 | 3-12 | 1-3 maintaining, briefing for everyone | 3-9 |
Formatdifferent | Workshop | Workshop | Async | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Affinity Size Map, Grouped Estimates, Unclear Items | RAID Log, Status Report Source | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | AlignmentStakeholdersTeam | EstimationBacklogRelative sizing | RiskTrackingStakeholdersGovernance | EstimationAgileRelative sizingTeam |