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 Architecture Decision Record | ![]() Agile Sprint 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 30-60 min | 15-45 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 1-3 | Scrum Team |
Formatdifferent | Workshop | Async | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | ADR File, Decision Log, Rationale | Improvement actions, Team agreements |
Tagsno overlap | RetrospectiveImprovementTeamReflection | ArchitectureRationaleDocumentationGovernance | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






