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
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Learning Review.
Operations
Learning Review
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.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.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.
Complexitydifferent
LowMediumMediumLow
Timedifferent
45-90 min1-3 h1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
2-83-103-10Scrum Team
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
RACI Matrix, Responsibility Map, Decision NotesProcess Map, Handoff List, Improvement BacklogLearning Review Notes, System Factors, Improvement ActionsImprovement actions, Team agreements
Tagsno overlap
RolesResponsibilityGovernanceOperations
ProcessOperationsImprovement
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementLearning
Add more methods