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 UpATAM (Architecture Tradeoff Analysis Method)Bounded Context CanvasLASR (Lightweight Approach for Software Reviews)
| Criterion |  Delivery Shape Up |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Domain Modeling Bounded Context Canvas |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-4 pro Pitch | Evaluation team, architects, and relevant stakeholders | 3-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Context Canvas, Glossary, Integration Notes | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks |
Tagsno overlap | PlanningDeliveryAutonomy | ArchitectureQualityRiskTradeoffsStakeholders | Domain-Driven DesignBoundariesModeling | ArchitectureQualityRiskAssessmentLean |