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 Start Stop Continue |  Agile Sprint Retrospective |  Agile Mad Sad Glad |
|---|---|---|---|---|
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 team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 60-90 min | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min |
Participantsdifferent | 4-12 | 3-12 | Scrum Team | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements | Emotion Board, Themes, Action Items |
Tagsno overlap | RiskArchitectureWorkshopValidation | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning | RetrospectiveTeamReflection |