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 Fishbowl Discussion.
Facilitation
Fishbowl Discussion
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.When a controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover.
Complexitydifferent
MediumLowMedium
Timedifferent
1-2 hUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter45-90 min
Participantsdifferent
3-12Scrum Team8-80
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsImprovement actions, Team agreementsDiscussion Insights, Observed Tensions, Follow-up Questions
Tagsno overlap
Systems thinkingTradeoffsLeadership
RetrospectiveImprovementLearning
FacilitationDialogueLarge group
Add more methods

Often compared together

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

Paper illustration for Peer Instruction.
Knowledge Modeling
Peer Instruction
Paper illustration for World Café.
Facilitation
World Café
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