View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Shape UpContext MapATAM (Architecture Tradeoff Analysis Method)Architecture Communication Canvas
| Criterion |  Delivery Shape Up |  Domain Modeling Context Map |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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 several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 60-120 min |
Participantsdifferent | 2-4 pro Pitch | 2-8 | Evaluation team, architects, and relevant stakeholders | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Context Map, Integration Patterns, Boundary Notes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | PlanningDeliveryAutonomy | Domain-Driven DesignBoundariesStrategy | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureCommunicationStakeholdersCanvas |