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 Scrum |  Facilitation Consensus Workshop |  Facilitation Stakeholder Salience Model |
|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | When a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 60-90 min |
Participantsdifferent | 3-10 (Scrum Team) | 5-30 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Consensus Clusters, Theme Titles, Priority Areas | Salience Diagram, Strategy per Class |
Tagsno overlap | AgileIterationCadence | FacilitationConsensusWorkshopAlignment | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
