View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Shape Up |  Facilitation Expectation Mapping |  Architecture Software Architecture Canvas |  Delivery Communication Plan |
|---|---|---|---|---|
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 people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 45-90 min | 1-2 h | 45-90 min |
Participantsdifferent | 2-4 pro Pitch | 3-12 | 3-10 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Expectation Map, Alignment Notes, Agreements | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | PlanningDeliveryAutonomy | AlignmentStakeholdersTeam | CanvasArchitectureAlignmentWorkshop | CommunicationStakeholdersDeliveryPlanning |