methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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 should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
30 min Setup, dann laufend45–75 min3–4 h for initial assessment; preparation and deeper analysis additional30-60 min
Participantsdifferent
1-3 maintaining, briefing for everyoneTeam members involved1 or a small team; particularly suitable for 3–4 people3-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report Source4Ls Board, Learning Themes, Improvement ActionsLean 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 checksStart Stop Continue Board, Improvement Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
RetrospectiveLearningReflectionTeam
ArchitectureQualityRiskAssessmentLean
RetrospectiveImprovementTeamReflection
Add more methods