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 of Shape Up with its method-specific working model.
Delivery
Shape Up
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Purposedifferent
Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.
Complexitydifferent
MediumLowLowLow
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-Down45-90 min1-2 h30-60 min
Participantsdifferent
2-4 pro Pitch3-123-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesExpectation Map, Alignment Notes, AgreementsArchitecture Canvas, Goals, Constraints, Quality AttributesPower Interest Grid, Strategy per Stakeholder
Tagsno overlap
PlanningDeliveryAutonomy
AlignmentStakeholdersTeam
CanvasArchitectureAlignmentWorkshop
StakeholdersFacilitationAlignmentPlanning
Add more methods