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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for 8D Problem Solving.
Operations
8D 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.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
LowMediumHigh
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-4 h1-6 Wochen
Participantsdifferent
Scrum Team3-84-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Improvement actions, Team agreementsProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
RetrospectiveImprovementLearning
Root causeProblem solvingQualityIncident
QualityProblem solvingRoot cause
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 Tree Analysis
Operations
Root Cause Tree 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