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 C4 Model |  Agile Starfish Retrospective |  Agile Start Stop Continue |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 45-90 min | 30-60 min | 45–75 min |
Participantsdifferent | 1-5 | 4-12 | 3-12 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureCommunicationVisualization | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |