View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Constraint AnalysisARID (Active Reviews for Intermediate Designs)LASR (Lightweight Approach for Software Reviews)Pre-Mortem
| Criterion |  Decision Making Constraint Analysis |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Decision Making Pre-Mortem |
|---|---|---|---|---|
Purposedifferent | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 30-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 3–4 h for initial assessment; preparation and deeper analysis additional | 20–45 min |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 1 or a small team; particularly suitable for 3–4 people | Small cross-functional group |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | 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 |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureQualityRiskAssessmentLean | RiskDecisionFailurePlanning |