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 StormingSprint RetrospectiveATAM (Architecture Tradeoff Analysis Method)After-Action Review
| Criterion |  Architecture Risk Storming |  Agile Sprint Retrospective |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations After-Action Review |
|---|---|---|---|---|
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 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Low | Low | High | Low |
Timedifferent | 60-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | Several meetings plus preparation and analysis; total effort depends on scope | 20-45 min |
Participantsdifferent | 4-12 | Scrum Team | Evaluation team, architects, and relevant stakeholders | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Improvement actions, Team agreements | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Lessons learned, Action items, Event summary |
Tagsno overlap | RiskArchitectureWorkshopValidation | RetrospectiveImprovementLearning | ArchitectureQualityRiskTradeoffsStakeholders | LearningOperationsImprovement |