View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Process Mapping |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Sprint Retrospective |
|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | 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 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. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 1-3 h | 2–4 h review as a planning range; preparation and evaluation additional | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-10 | Designers, developers as users, and facilitation | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Improvement actions, Team agreements |
Tagsno overlap | ProcessOperationsImprovement | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
