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 Dot Voting |
|---|---|---|---|
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 a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 1-3 h | 5-15 min |
Participantsdifferent | 3-10 (Scrum Team) | 5-30 | 3-20 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | AgileIterationCadence | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






