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)Pre-MortemCost of DelayATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Pre-Mortem |  Delivery Cost of Delay |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | 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. | 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. |
Complexitydifferent | Medium | Low | High | High |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 20–45 min | 90-180 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | Small cross-functional group | 3-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
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 | Risk list, Mitigation plan, Assumption log | CoD Table, Prioritization Sequence | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | RiskDecisionFailurePlanning | PrioritizationDeliveryEconomicsDecision | ArchitectureQualityRiskTradeoffsStakeholders |