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 notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration for Time Blocking
Operations
Time Blocking
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.With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory.With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-2 h Setup, laufend15-30 min Planung, laufend10-20 min daily
Participantsdifferent
Scrum Team111
Formatdifferent
WorkshopAsyncAsyncAsync
Outputdifferent
Improvement actions, Team agreementsAction Lists, Project List, Review RoutineBlocked Calendar, Capacity View, Focus PlanDaily Plan, Time Estimates, Review Notes
Tagsno overlap
RetrospectiveImprovementLearning
ProductivityPlanningTasksExecution
PlanningTime managementFocus
PlanningTime managementProductivityOperations
Add more methods