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 for Weekly Review.
Operations
Weekly Review
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
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
In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.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.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 min30-60 min10-20 min daily45–75 min
Participantsdifferent
13-121Team members involved
Formatdifferent
AsyncWorkshopAsyncWorkshop
Outputdifferent
Updated Task System, Weekly Focus, Next ActionsStart Stop Continue Board, Improvement ActionsDaily Plan, Time Estimates, Review Notes4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
ProductivityExecutionPlanning
RetrospectiveImprovementTeamReflection
PlanningTime managementProductivityOperations
RetrospectiveLearningReflectionTeam
Add more methods