View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Architecture Quality Attribute Workshop |  Facilitation Dot Estimation |  Agile Ideal Days |
|---|---|---|---|---|
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. | 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 size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 60-90 min | 2-4 h | 5-20 min | 15-60 min |
Participantsdifferent | 4-12 | 5-15 | 3-20 | 2-9 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Quality Scenarios, Priority List, Architecture Concerns | Effort Heatmap, Risk Signals, Discussion Targets | Ideal Day Estimates, Assumption Notes, Capacity Caveats |
Tagsno overlap | RiskArchitectureWorkshopValidation | RequirementsArchitectureWorkshop | EstimationEffortRisk | EstimationEffortAgile |