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 4Ls Retrospective |  Architecture Risk Storming |  Architecture ARID (Active Reviews for Intermediate Designs) |  Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time. | 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. | 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 team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 45–75 min | 60-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min |
Participantsdifferent | Team members involved | 4-12 | Designers, developers as users, and facilitation | 3-10 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Annotated Diagram, Prioritized Risk List, Action Backlog | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Emotion Board, Themes, Action Items |
Tagsno overlap | RetrospectiveLearningReflectionTeam | RiskArchitectureWorkshopValidation | ArchitectureEngineeringFeedbackValidationTasks | RetrospectiveTeamReflection |