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:Risk Storming Sailboat Retrospective Start Stop Continue ARID (Active Reviews for Intermediate Designs)

Criterion	Architecture Risk Storming	Agile Sailboat Retrospective	Agile Start Stop Continue	Architecture ARID (Active Reviews for Intermediate Designs)
Purposedifferent	Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.	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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.	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.
Complexitydifferent	Low	Low	Low	Medium
Timedifferent	60-90 min	45-90 min	30-60 min	2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent	4-12	4-12	3-12	Designers, developers as users, and facilitation
Formatdifferent	Workshop	Workshop	Workshop	Workshop + async
Outputdifferent	Annotated Diagram, Prioritized Risk List, Action Backlog	Sailboat Board, Risks, Improvement Actions	Start Stop Continue Board, Improvement Actions	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap	RiskArchitectureWorkshopValidation	RetrospectiveTeamImprovement	RetrospectiveImprovementTeamReflection	ArchitectureEngineeringFeedbackValidationTasks

Add more methods