View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Start Stop Continue |  Agile Starfish Retrospective |
|---|---|---|---|
Purposedifferent | 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. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min | 45-90 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | 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 | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
