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 Start Stop Continue |  Architecture Software Architecture Canvas |  Agile Mad Sad Glad |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-60 min | 1-2 h | 30-60 min | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 3-10 | 4-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Architecture Canvas, Goals, Constraints, Quality Attributes | Emotion Board, Themes, Action Items | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | RetrospectiveImprovementTeamReflection | CanvasArchitectureAlignmentWorkshop | RetrospectiveTeamReflection | RetrospectiveImprovementExperimentsTeam |