methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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.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 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 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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
30-90 min1-2 h2-5 min je Item1-3 h
Participantsdifferent
3-123-103-95-30
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsArchitecture Canvas, Goals, Constraints, Quality AttributesRelative Estimates, Assumption Notes, Split CandidatesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
EstimationBacklogRelative sizing
CanvasArchitectureAlignmentWorkshop
EstimationAgileRelative sizingTeam
FacilitationConsensusWorkshopAlignment
Add more methods