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 Accountability Ladder
Operations
Accountability Ladder
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 Starfish Retrospective
Agile
Starfish Retrospective
Purposedifferent
With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on.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 improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued.
Complexitysame
LowLowLowLow
Timedifferent
20-45 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter30-60 min45-90 min
Participantsdifferent
1-8Scrum Team3-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Ownership Reflection, Action Commitment, Coaching NotesImprovement actions, Team agreementsEmotion Board, Themes, Action ItemsStarfish Board, Practice Changes, Experiments
Tagsno overlap
ResponsibilityLeadershipTeam
RetrospectiveImprovementLearning
RetrospectiveTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods