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:Mad Sad Glad LASR (Lightweight Approach for Software Reviews)Start Stop Continue Sailboat Retrospective

Criterion	Agile Mad Sad Glad	Architecture LASR (Lightweight Approach for Software Reviews)	Agile Start Stop Continue	Agile Sailboat Retrospective
Purposedifferent	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.	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 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.
Complexitydifferent	Low	Medium	Low	Low
Timedifferent	30-60 min	3–4 h for initial assessment; preparation and deeper analysis additional	30-60 min	45-90 min
Participantsdifferent	3-10	1 or a small team; particularly suitable for 3–4 people	3-12	4-12
Formatdifferent	Workshop	Workshop + async	Workshop	Workshop
Outputdifferent	Emotion Board, Themes, Action Items	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	Sailboat Board, Risks, Improvement Actions
Tagsno overlap	RetrospectiveTeamReflection	ArchitectureQualityRiskAssessmentLean	RetrospectiveImprovementTeamReflection	RetrospectiveTeamImprovement

Add more methods