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)Sprint Retrospective 4Ls Retrospective Mad Sad Glad

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Agile Sprint Retrospective	Agile 4Ls Retrospective	Agile Mad Sad Glad
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 sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.	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.	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	Medium	Low	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter	45–75 min	30-60 min
Participantsdifferent	Designers, developers as users, and facilitation	Scrum Team	Team members involved	3-10
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Improvement actions, Team agreements	4Ls Board, Learning Themes, Improvement Actions	Emotion Board, Themes, Action Items
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	RetrospectiveImprovementLearning	RetrospectiveLearningReflectionTeam	RetrospectiveTeamReflection

Add more methods