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 |  Facilitation Team Charter |  Facilitation Expectation Mapping |  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 team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45–75 min | 2-4 h | 45-90 min | 30-60 min |
Participantsdifferent | Team members involved | 3-12 | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Team Charter, Working Norms, Role Notes | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions |
Tags1 shared | RetrospectiveLearningReflectionTeam | TeamAlignmentCollaboration | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection |