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 Mad Sad Glad |  DevOps ChatOps |  Architecture Risk Storming |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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. | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 30-60 min | Ongoing | 60-90 min | 30-60 min |
Participantsdifferent | 3-10 | 2-20 | 4-12 | 3-12 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Emotion Board, Themes, Action Items | Chat Transcript, Action Log, Automations | Annotated Diagram, Prioritized Risk List, Action Backlog | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveTeamReflection | CollaborationEngineeringIncident | RiskArchitectureWorkshopValidation | RetrospectiveImprovementTeamReflection |