View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Sprint Retrospective |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Assumption Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | Medium |
Timedifferent | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 2–4 h review as a planning range; preparation and evaluation additional | 45-60 min |
Participantsdifferent | Scrum Team | Designers, developers as users, and facilitation | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Improvement actions, Team agreements | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RetrospectiveImprovementLearning | ArchitectureEngineeringFeedbackValidationTasks | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
