View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Sprint RetrospectiveLASR (Lightweight Approach for Software Reviews)Failure Mode and Effects Analysis
| Criterion |  Agile Sprint Retrospective |  Architecture LASR (Lightweight Approach for Software Reviews) |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|
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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | Medium | High |
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 | 2-6 h |
Participantsdifferent | Scrum Team | 1 or a small team; particularly suitable for 3–4 people | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
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 | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | RetrospectiveImprovementLearning | ArchitectureQualityRiskAssessmentLean | RiskQualityOperationsRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
