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-MortemLASR (Lightweight Approach for Software Reviews)ARID (Active Reviews for Intermediate Designs)Risk Matrix
| Criterion |  Decision Making Pre-Mortem |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ARID (Active Reviews for Intermediate Designs) |  Decision Making Risk Matrix |
|---|---|---|---|---|
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. | 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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 20–45 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min |
Participantsdifferent | Small cross-functional group | 1 or a small team; particularly suitable for 3–4 people | Designers, developers as users, and facilitation | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Risk list, Mitigation plan, Assumption log | 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 | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Risk Matrix, Top Risk List |
Tagsno overlap | RiskDecisionFailurePlanning | ArchitectureQualityRiskAssessmentLean | ArchitectureEngineeringFeedbackValidationTasks | RiskDecisionPrioritizationAssessment |