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
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 of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Peer Instruction.
Knowledge Modeling
Peer Instruction
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Purposedifferent
When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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.Peer Instruction uses group thinking to clarify difficult terms or concepts faster. The method combines individual reflection with social correction and shared precision.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
45–75 min30-60 min10-20 min je Frage45-90 min
Participantsdifferent
Team members involved3-126-504-12
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsStart Stop Continue Board, Improvement ActionsConcept Questions, Vote Results, Learning NotesStarfish Board, Practice Changes, Experiments
Tagsno overlap
RetrospectiveLearningReflectionTeam
RetrospectiveImprovementTeamReflection
LearningDialogueFacilitation
RetrospectiveImprovementExperimentsTeam
Add more methods