View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Fault IsolationLASR (Lightweight Approach for Software Reviews)Stakeholder Salience ModelRAID Log
| Criterion |  Engineering Fault Isolation |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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 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. | 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 | 30-180 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-6 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | 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 | Salience Diagram, Strategy per Class | RAID Log, Status Report Source |
Tagsno overlap | TroubleshootingDiagnosisEngineering | ArchitectureQualityRiskAssessmentLean | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |