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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 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.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
LowLowMediumMedium
Timedifferent
20-40 min initial, dann laufend1-2 h1-2 h1-3 h
Participantsdifferent
3-153-104-125-30
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
ROAM Board, Owner ListArchitecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision QuestionsConsensus Clusters, Theme Titles, Priority Areas
Tags1 shared
RiskAgileTrackingAlignment
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
FacilitationConsensusWorkshopAlignment
Add more methods