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 Mad Sad Glad
Agile
Mad Sad Glad
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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.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.When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood.
Complexitysame
LowLowLowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-60 min45-90 min30-60 min
Participantsdifferent
Scrum Team3-104-123-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsEmotion Board, Themes, Action ItemsSailboat Board, Risks, Improvement ActionsStart Stop Continue Board, Improvement Actions
Tags1 shared
RetrospectiveImprovementLearning
RetrospectiveTeamReflection
RetrospectiveTeamImprovement
RetrospectiveImprovementTeamReflection
Add more methods