View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations After-Action Review |  Delivery RAID Log |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|
Purposedifferent | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | 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 |
Tagsno overlap | LearningOperationsImprovement | RiskTrackingStakeholdersGovernance | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
