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)Bottleneck Analysis Risk Storming Goal Question Metric

Criterion	Architecture ARID (Active Reviews for Intermediate Designs)	Operations Bottleneck Analysis	Architecture Risk Storming	Engineering Goal Question Metric
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.	For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.	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.	Helps clarify technical problems, hypotheses, and next steps in concrete terms. It breaks a technical problem into testable parts. The result is captured as a GQM table and metric briefs.
Complexitydifferent	Medium	Medium	Low	Medium
Timedifferent	2–4 h review as a planning range; preparation and evaluation additional	1-3 h	60-90 min	90-180 min
Participantsdifferent	Designers, developers as users, and facilitation	3-8	4-12	3-6
Formatdifferent	Workshop + async	Workshop + async	Workshop	Workshop
Outputdifferent	Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions	Bottleneck Map, Flow Metrics, Improvement Options, Follow-up Measures	Annotated Diagram, Prioritized Risk List, Action Backlog	GQM Table, Metric Profiles
Tagsno overlap	ArchitectureEngineeringFeedbackValidationTasks	FlowMeasurementConstraints	RiskArchitectureWorkshopValidation	MetricsMeasurementEngineeringAlignment

Add more methods