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
Story Splitting method illustration showing its working structure
Agile
Story Splitting
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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.When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
30-90 min30-60 min1-2 h1-3 h
Participantsdifferent
3-122-63-105-30
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Affinity Size Map, Grouped Estimates, Unclear ItemsSmaller Stories, Acceptance Criteria, Split RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
EstimationBacklogRelative sizing
BacklogIterationDelivery
CanvasArchitectureAlignmentWorkshop
FacilitationConsensusWorkshopAlignment
Add more methods