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 Stakeholder Salience Model |  Facilitation Expectation 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 2-5 min je Item | 60-90 min | 45-90 min |
Participantsdifferent | 3-9 | 3-6 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Salience Diagram, Strategy per Class | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | EstimationAgileRelative sizingTeam | StakeholdersFacilitationAlignmentGovernance | AlignmentStakeholdersTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
