View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Pre-MortemATAM (Architecture Tradeoff Analysis Method)LASR (Lightweight Approach for Software Reviews)Communication Plan
| Criterion |  Decision Making Pre-Mortem |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Low | High | Medium | Low |
Timedifferent | 20–45 min | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min |
Participantsdifferent | Small cross-functional group | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | 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 | RiskDecisionFailurePlanning | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | CommunicationStakeholdersDeliveryPlanning |