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 Affinity Estimation |  Facilitation Stakeholder Salience Model |  Agile Planning Poker |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 30-90 min | 60-90 min | 2-5 min je Item | 1-2 h |
Participantsdifferent | 3-12 | 3-6 | 3-9 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Affinity Size Map, Grouped Estimates, Unclear Items | Salience Diagram, Strategy per Class | Relative Estimates, Assumption Notes, Split Candidates | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | EstimationBacklogRelative sizing | StakeholdersFacilitationAlignmentGovernance | EstimationAgileRelative sizingTeam | AlignmentStakeholdersStrategyFacilitation |