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 Learning Review.
Operations
Learning Review
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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
LowMediumMediumLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-2 h Setup, laufend1-3 h10-20 min daily
Participantsdifferent
Scrum Team13-101
Formatdifferent
WorkshopAsyncWorkshopAsync
Outputdifferent
Improvement actions, Team agreementsAction Lists, Project List, Review RoutineLearning Review Notes, System Factors, Improvement ActionsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
RetrospectiveImprovementLearning
ProductivityPlanningTasksExecution
LearningRetrospectiveIncidentOperations
PlanningTime managementProductivityOperations
Add more methods