methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration for Eat the Frog
Operations
Eat the Frog
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls 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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.The method protects energy and attention for the task that creates the largest progress and is often postponed.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
LowLowLowLow
Timedifferent
30-60 min10-20 min daily15-90 min daily45–75 min
Participantsdifferent
3-1211Team members involved
Formatdifferent
WorkshopAsyncAsyncWorkshop
Outputdifferent
Start Stop Continue Board, Improvement ActionsDaily Plan, Time Estimates, Review NotesPriority Task, Completion Note, Daily Focus4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
RetrospectiveImprovementTeamReflection
PlanningTime managementProductivityOperations
PrioritizationProductivityFocusExecution
RetrospectiveLearningReflectionTeam
Add more methods