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 WSJF |  Architecture Software Architecture Canvas |  Facilitation Consensus Workshop |  Facilitation Dot Voting |
|---|---|---|---|---|
Purposedifferent | When many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 | High | Low | Medium | Low |
Timedifferent | 45-90 min | 1-2 h | 1-3 h | 5-15 min |
Participantsdifferent | 3-10 | 3-10 | 5-30 | 3-20 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Ranked Backlog, Cost-of-Delay Assumptions | Architecture Canvas, Goals, Constraints, Quality Attributes | Consensus Clusters, Theme Titles, Priority Areas | Ranked list, Consensus signal, Shortlist |
Tagsno overlap | LeanEconomicsSequencePrioritization | CanvasArchitectureAlignmentWorkshop | FacilitationConsensusWorkshopAlignment | FacilitationVotingConsensusPrioritization |