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:ARID (Active Reviews for Intermediate Designs)Start Stop Continue Root Cause Analysis 4Ls Retrospective

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Agile Start Stop Continue	Operations Root Cause Analysis	Agile 4Ls Retrospective
Purposedifferent	ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.	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 problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.	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.
Complexitydifferent	Medium	Low	Medium	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	30-60 min	1-4 h	45–75 min
Participantsdifferent	Designers, developers as users, and facilitation	3-12	3-8	Team members involved
Formatdifferent	Workshop + async	Workshop	Workshop + async	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Start Stop Continue Board, Improvement Actions	Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan	4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	RetrospectiveImprovementTeamReflection	Root causeProblem solvingQualityIncident	RetrospectiveLearningReflectionTeam

Add more methods