View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:MoSCoWSAAM (Software Architecture Analysis Method)Assumption SurfacingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Delivery MoSCoW |  Architecture SAAM (Software Architecture Analysis Method) |  Decision Making Assumption Surfacing |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | Low | High | Low | Medium |
Timedifferent | 30-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-12 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized Backlog, Release Scope, Tradeoff Notes | 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 | Assumption List, Critical Assumptions, Learning Plan | 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 | PrioritizationScopeDecision | ArchitectureChangeAnalysisComparisonQuality | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskAssessmentLean |