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)Quality Attribute Workshop Start Stop Continue 4Ls Retrospective

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Architecture Quality Attribute Workshop	Agile Start Stop Continue	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.	A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties.	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 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	Medium	Low	Low
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	2-4 h	30-60 min	45–75 min
Participantsdifferent	Designers, developers as users, and facilitation	5-15	3-12	Team members involved
Formatdifferent	Workshop + async	Workshop	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Quality Scenarios, Priority List, Architecture Concerns	Start Stop Continue Board, Improvement Actions	4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	RequirementsArchitectureWorkshop	RetrospectiveImprovementTeamReflection	RetrospectiveLearningReflectionTeam

Add more methods