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 Delegation Poker.
Facilitation
Delegation Poker
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
LowLowMediumLow
Timedifferent
45-90 min1-2 h1-2 h1-2 h
Participantsdifferent
3-103-104-123-8
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsArchitecture Canvas, Goals, Constraints, Quality AttributesAlignment Map, Open Issues, Decision QuestionsInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
AutonomyRolesTeam
CanvasArchitectureAlignmentWorkshop
AlignmentStakeholdersStrategyFacilitation
AlignmentArchitectureCanvas
Add more methods