View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Facilitation Timeline | ![]() Agile Sprint Retrospective | ![]() Facilitation Barcamp | ![]() Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | When a project, incident, or change process is only remembered in fragments, Timeline brings the sequence back into a readable form. It makes turning points, precursors, and after-effects recognizable over the course of time. | 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 many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | Halber Tag bis 2 Tage | 45–75 min |
Participantsdifferent | 2-12 | Scrum Team | 15-200 | Team members involved |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Timeline, Milestones, Insight Notes | Improvement actions, Team agreements | Session Board, Session Notes, Community Learnings | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | TimelineFacilitationSequence | RetrospectiveImprovementLearning | FacilitationLarge groupLearning | RetrospectiveLearningReflectionTeam |



