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 |  Agile Sprint Retrospective |  Product Discovery Assumption Mapping |  Agile Starfish Retrospective |
|---|---|---|---|---|
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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 60-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45-60 min | 45-90 min |
Participantsdifferent | 4-12 | Scrum Team | 2-8 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Improvement actions, Team agreements | Assumption map, Test backlog, Risk ranking | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RiskArchitectureWorkshopValidation | RetrospectiveImprovementLearning | AssumptionsRiskExperimentsValidation | RetrospectiveImprovementExperimentsTeam |