View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Delivery Shape Up |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 45-90 min | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-2 h |
Participantsdifferent | 3-12 | 2-4 pro Pitch | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | AlignmentStakeholdersTeam | PlanningDeliveryAutonomy | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
