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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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 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.
Complexitydifferent
LowLowMediumMedium
Timedifferent
1-2 h20-40 min initial, dann laufend1-3 h1-2 h
Participantsdifferent
3-103-155-304-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Architecture Canvas, Goals, Constraints, Quality AttributesROAM Board, Owner ListConsensus Clusters, Theme Titles, Priority AreasAlignment Map, Open Issues, Decision Questions
Tags1 shared
CanvasArchitectureAlignmentWorkshop
RiskAgileTrackingAlignment
FacilitationConsensusWorkshopAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods