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
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 for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Purposedifferent
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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
MediumLowMediumMedium
Timedifferent
30-60 min1-2 h1-2 h1-3 h
Participantsdifferent
2-63-104-125-30
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Smaller Stories, Acceptance Criteria, Split RationaleArchitecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision QuestionsConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
BacklogIterationDelivery
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
FacilitationConsensusWorkshopAlignment
Add more methods