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 |  Domain Modeling Context Map |  Architecture Architecture Decision Record |  Domain Modeling Bounded Context 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-3 h | 15-45 min | 1-3 h |
Participantsdifferent | 2-4 pro Pitch | 2-8 | 1-3 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Context Map, Integration Patterns, Boundary Notes | ADR File, Decision Log, Rationale | Context Canvas, Glossary, Integration Notes |
Tagsno overlap | PlanningDeliveryAutonomy | Domain-Driven DesignBoundariesStrategy | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesModeling |