View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Business Strategy Value Chain Analysis |  Architecture Risk Storming |
|---|---|---|---|
Purposedifferent | 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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | High | Low |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | Half day | 60-90 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 3-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | 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 | Value Chain Map, Lever List | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | StrategyBusiness modelDiagnosisAnalysis | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
