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 ROAM Board |  Agile Planning Poker |
|---|---|---|---|---|
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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 | Medium | Medium | Low | Low |
Timedifferent | 30-90 min | 60-90 min | 20-40 min initial, dann laufend | 2-5 min je Item |
Participantsdifferent | 3-12 | 3-6 | 3-15 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Affinity Size Map, Grouped Estimates, Unclear Items | Salience Diagram, Strategy per Class | ROAM Board, Owner List | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | EstimationBacklogRelative sizing | StakeholdersFacilitationAlignmentGovernance | RiskAgileTrackingAlignment | EstimationAgileRelative sizingTeam |