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 4Ls Retrospective | ![]() Agile Acceptance Criteria Workshop | ![]() Agile Start Stop Continue |
|---|---|---|---|
Purposedifferent | 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. | When a story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 45–75 min | 20-40 min pro Story | 30-60 min |
Participantsdifferent | Team members involved | 3-6 | 3-12 |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Acceptance Criteria, Story Update | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | RetrospectiveLearningReflectionTeam | AgileRequirementsRefinementBehavior-Driven Development | RetrospectiveImprovementTeamReflection |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






