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 Current Reality Tree
Systems Thinking
Current Reality Tree
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.A Current Reality Tree condenses many symptoms into a few causal chains. The method makes visible which core problems drive several negative effects at once.
Complexitydifferent
LowHigh
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter2-6 h
Participantsdifferent
Scrum Team3-8
Formatsame
WorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsCurrent Reality Tree, Core Problems, Intervention Ideas
Tagsno overlap
RetrospectiveImprovementLearning
Systems thinkingRoot causeConstraintsCausality
Add more methods

Often compared together

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

Paper illustration for Theory of Constraints Thinking Process.
Systems Thinking
Theory of Constraints Thinking Process
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 of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Causal Factor Analysis.
Operations
Causal Factor Analysis