View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:LASR (Lightweight Approach for Software Reviews)WSJFATAM (Architecture Tradeoff Analysis Method)Cost of Delay
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile WSJF |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery Cost of Delay |
|---|---|---|---|---|
Purposedifferent | 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 tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together. | 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. | Helps clarify scope, order, and delivery flow in concrete terms. It makes work, constraints, and sequence manageable. The result is captured as a Cost of Delay table and prioritization sequence. |
Complexitydifferent | Medium | High | High | High |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 90-180 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 3-10 | Evaluation team, architects, and relevant stakeholders | 3-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | 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 | Ranked Backlog, Cost-of-Delay Assumptions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | CoD Table, Prioritization Sequence |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | LeanEconomicsSequencePrioritization | ArchitectureQualityRiskTradeoffsStakeholders | PrioritizationDeliveryEconomicsDecision |