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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper illustration for ALPEN Method
Operations
ALPEN Method
Purposedifferent
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.For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.The method protects energy and attention for the task that creates the largest progress and is often postponed.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.
Complexitysame
LowLowLowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter25 min Zyklen15-90 min daily10-20 min daily
Participantsdifferent
Scrum Team111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Improvement actions, Team agreementsFocus Sessions, Task Progress, Interruption NotesPriority Task, Completion Note, Daily FocusDaily Plan, Time Estimates, Review Notes
Tagsno overlap
RetrospectiveImprovementLearning
FocusTime managementProductivityExecution
PrioritizationProductivityFocusExecution
PlanningTime managementProductivityOperations
Add more methods