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 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 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
LowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter10-20 min daily
Participantsdifferent
Scrum Team1
Formatdifferent
WorkshopAsync
Outputdifferent
Improvement actions, Team agreementsDaily Plan, Time Estimates, Review Notes
Tagsno overlap
RetrospectiveImprovementLearning
PlanningTime managementProductivityOperations
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Learning Review.
Operations
Learning Review
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
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done