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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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 single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitysame
LowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter15-30 min
Participantsdifferent
Scrum Team2-6
Formatsame
WorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsRoot cause notes, Countermeasures
Tagsno overlap
RetrospectiveImprovementLearning
Root causeIncidentLeanProblem solving
Add more methods

Often compared together

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

Paper illustration for Learning Review.
Operations
Learning Review
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 illustration for 8D Problem Solving.
Operations
8D Problem Solving