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 Tree Analysis
Operations
Root Cause Tree Analysis
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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
LowMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter1-3 h
Participantsdifferent
Scrum Team2-8
Formatsame
WorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
RetrospectiveImprovementLearning
Root causeTreeIncidentQuality
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