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 Start Stop Continue |  Agile Sprint Retrospective |  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 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 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 | 30-60 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min |
Participantsdifferent | 1-5 | 3-12 | Scrum Team | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Start Stop Continue Board, Improvement Actions | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | ArchitectureCommunicationVisualization | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam |