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 |  Agile Sprint Retrospective |  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. | 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. |
Complexitydifferent | Low | Low | Medium |
Timedifferent | 30 min Setup, dann laufend | 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 |
Participantsdifferent | 1-3 maintaining, briefing for everyone | Scrum Team | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | 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 |
Tagsno overlap | RiskTrackingStakeholdersGovernance | RetrospectiveImprovementLearning | ArchitectureQualityRiskAssessmentLean |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
