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 UpSAAM (Software Architecture Analysis Method)LASR (Lightweight Approach for Software Reviews)Communication Plan
| Criterion |  Delivery Shape Up |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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. | 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 | High | Medium | Low |
Timedifferent | 6 Wochen Cycle + 2 Wochen Cool-Down | Preparation, scenario analysis, and findings review; effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | 2-4 pro Pitch | Architecture experts and stakeholders for scenarios and weighting | 1 or a small team; particularly suitable for 3–4 people | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | 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 | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | PlanningDeliveryAutonomy | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskAssessmentLean | CommunicationStakeholdersDeliveryPlanning |