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
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration for Ivy Lee Method
Operations
Ivy Lee 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.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.With a restless workday full of too many open items, the method creates radical simplicity. It directs attention to a short sequence instead of a broad, still-open field.
Complexitysame
LowLowLowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter15-90 min daily10-20 min daily5-10 min daily
Participantsdifferent
Scrum Team111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Improvement actions, Team agreementsPriority Task, Completion Note, Daily FocusDaily Plan, Time Estimates, Review NotesDaily Priority List, Completion Notes
Tagsno overlap
RetrospectiveImprovementLearning
PrioritizationProductivityFocusExecution
PlanningTime managementProductivityOperations
PrioritizationProductivityExecution
Add more methods