View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Innovation SCAMPER |
|---|---|---|---|
Purposedifferent | 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. | 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. | For an existing solution under pressure to change, the method deliberately opens space for systematic variants. It directs attention to rebuilding, combining, and repurposing rather than only new basic ideas. This produces concrete evolution paths for products, offerings, or workflows. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people | 2-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | 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 | SCAMPER Idea List, Concept Shortlist, Variation Notes |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean | BrainstormingIdeationCreativityReframingInnovation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






