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 Team Charter | ![]() Facilitation Alignment Mapping | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 2-5 min je Item | 2-4 h | 1-2 h | 60-90 min |
Participantsdifferent | 3-9 | 3-12 | 4-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Relative Estimates, Assumption Notes, Split Candidates | Team Charter, Working Norms, Role Notes | Alignment Map, Open Issues, Decision Questions | Salience Diagram, Strategy per Class |
Tagsno overlap | EstimationAgileRelative sizingTeam | TeamAlignmentCollaboration | AlignmentStakeholdersStrategyFacilitation | StakeholdersFacilitationAlignmentGovernance |



