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 CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for Learning Review.
Operations
Learning Review
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.CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.
Complexitydifferent
LowMediumMedium
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-90 min1-3 h
Participantsdifferent
Scrum Team3-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Improvement actions, Team agreementsCATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsLearning Review Notes, System Factors, Improvement Actions
Tagsno overlap
RetrospectiveImprovementLearning
Systems thinkingFramingStakeholders
LearningRetrospectiveIncidentOperations
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
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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem