View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Business Model Stress TestLASR (Lightweight Approach for Software Reviews)Stakeholder Salience ModelRAID Log
| Criterion |  Business Strategy Business Model Stress Test |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Stakeholder Salience Model |  Delivery RAID Log |
|---|---|---|---|---|
Purposedifferent | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | Medium | Medium | Low |
Timedifferent | Half day | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min | 30 min Setup, dann laufend |
Participantsdifferent | 3-8 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop | Workshop + async | Workshop | Async |
Outputdifferent | Stress Test Report, Action Plan per Scenario | 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 | StrategyBusiness modelRiskDiagnosis | ArchitectureQualityRiskAssessmentLean | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance |