View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sprint Retrospective |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations After-Action Review |
|---|---|---|---|
Purposedifferent | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 3–4 h for initial assessment; preparation and deeper analysis additional | 20-45 min |
Participantsdifferent | Scrum Team | 1 or a small team; particularly suitable for 3–4 people | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | 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 | Lessons learned, Action items, Event summary |
Tagsno overlap | RetrospectiveImprovementLearning | ArchitectureQualityRiskAssessmentLean | LearningOperationsImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
