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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
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 a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.
Complexitydifferent
LowMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-90 min
Participantsdifferent
Scrum Team2-5
Formatdifferent
WorkshopWorkshop + async
Outputdifferent
Improvement actions, Team agreementsA3 Report, Action Plan, Root Cause Analysis
Tagsno overlap
RetrospectiveImprovementLearning
LeanProblem solvingCoachingOperations
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