View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Failure Scenario AnalysisStakeholder Salience ModelLASR (Lightweight Approach for Software Reviews)RAID Log
| Criterion |  Engineering Failure Scenario Analysis |  Facilitation Stakeholder Salience Model |  Architecture LASR (Lightweight Approach for Software Reviews) |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 1-3 h | 60-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop | Workshop + async | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Salience Diagram, Strategy per Class | 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 | RAID Log, Status Report Source |
Tagsno overlap | FailureResilienceRisk | StakeholdersFacilitationAlignmentGovernance | ArchitectureQualityRiskAssessmentLean | RiskTrackingStakeholdersGovernance |