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 |  Decision Making Assumption Surfacing |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | 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 |
Tags1 shared | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
