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 a Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
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 Accountability Ladder
Operations
Accountability Ladder
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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.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.
Complexitydifferent
MediumLowLow
Timedifferent
1-2 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter20-45 min
Participantsdifferent
3-12Scrum Team1-8
Formatdifferent
WorkshopWorkshopWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsImprovement actions, Team agreementsOwnership Reflection, Action Commitment, Coaching Notes
Tagsno overlap
Systems thinkingTradeoffsLeadership
RetrospectiveImprovementLearning
ResponsibilityLeadershipTeam
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 for Sailboat Retrospective
Agile
Sailboat Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue