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 Causal Factor Analysis.
Operations
Causal Factor 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 an event with a complicated course, the method breaks down the contributing factors along the timeline. It shows how conditions, decisions, and reactions together produce a course of events.
Complexitydifferent
LowHigh
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter2-6 h
Participantsdifferent
Scrum Team3-10
Formatdifferent
WorkshopWorkshop + async
Outputdifferent
Improvement actions, Team agreementsEvent Timeline, Causal Factor Chart, Cause List, Corrective Actions
Tagsno overlap
RetrospectiveImprovementLearning
CausalityIncidentRoot causeTimeline
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
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