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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.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.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.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
6 Wochen Cycle + 2 Wochen Cool-DownSeveral meetings plus preparation and analysis; total effort depends on scope1-3 h1-3 h
Participantsdifferent
2-4 pro PitchEvaluation team, architects, and relevant stakeholders3-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Pitches, Bet-table decisions, Hill charts, Cooldown outcomesPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsContext Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
PlanningDeliveryAutonomy
ArchitectureQualityRiskTradeoffsStakeholders
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
Add more methods