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 Responsibility Poker.
Facilitation
Responsibility Poker
Paper session grid with two time blocks, three rooms, colored session cards and an open topic pool.
Facilitation
Barcamp
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 it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences.When many people can contribute knowledge and the flow should stay open, Barcamp provides a framework for self-organized sessions. The format channels energy without defining the content too narrowly in advance.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.
Complexitydifferent
LowMediumLow
Timedifferent
45-90 minHalber Tag bis 2 Tage30-60 min
Participantsdifferent
3-1015-2003-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Responsibility Map, Role Agreements, Open QuestionsSession Board, Session Notes, Community LearningsStart Stop Continue Board, Improvement Actions
Tagsno overlap
RolesResponsibilityTeamFacilitation
FacilitationLarge groupLearning
RetrospectiveImprovementTeamReflection
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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective