Compare

View methods side by side.

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

Selected:Start Stop Continue LASR (Lightweight Approach for Software Reviews)Sailboat Retrospective Mad Sad Glad

Criterion	Agile Start Stop Continue	Architecture LASR (Lightweight Approach for Software Reviews)	Agile Sailboat Retrospective	Agile Mad Sad Glad
Purposedifferent	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.	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 read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.	When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent	Low	Medium	Low	Low
Timedifferent	30-60 min	3–4 h for initial assessment; preparation and deeper analysis additional	45-90 min	30-60 min
Participantsdifferent	3-12	1 or a small team; particularly suitable for 3–4 people	4-12	3-10
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Start Stop Continue Board, Improvement Actions	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	Sailboat Board, Risks, Improvement Actions	Emotion Board, Themes, Action Items
Tagsno overlap	RetrospectiveImprovementTeamReflection	ArchitectureQualityRiskAssessmentLean	RetrospectiveTeamImprovement	RetrospectiveTeamReflection

Add more methods