View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Agile Start Stop Continue |  Agile Mad Sad Glad |  Agile Sailboat Retrospective |
|---|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Ongoing | 30-60 min | 30-60 min | 45-90 min |
Participantsdifferent | 2-12 | 3-12 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Start Stop Continue Board, Improvement Actions | Emotion Board, Themes, Action Items | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | FlowVisual managementDelivery | RetrospectiveImprovementTeamReflection | RetrospectiveTeamReflection | RetrospectiveTeamImprovement |