View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ARID (Active Reviews for Intermediate Designs)Game DaySailboat RetrospectiveStart Stop Continue
| Criterion |  Architecture ARID (Active Reviews for Intermediate Designs) |  DevOps Game Day |  Agile Sailboat Retrospective |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture. | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | High | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Halber Tag | 45-90 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 5-20 | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Simulation Notes, Gaps List, Updated Runbooks | Sailboat Board, Risks, Improvement Actions | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | ResilienceOperationsIncident | RetrospectiveTeamImprovement | RetrospectiveImprovementTeamReflection |