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 for Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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
When a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.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
LowLowMediumLow
Timedifferent
30-60 min45-90 min1-3 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
3-104-123-10Scrum Team
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Emotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsImprovement actions, Team agreements
Tags1 shared
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
LearningRetrospectiveIncidentOperations
RetrospectiveImprovementLearning
Add more methods