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 Peer Instruction.
Knowledge Modeling
Peer Instruction
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 Starfish Retrospective
Agile
Starfish Retrospective
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Purposedifferent
Peer Instruction uses group thinking to clarify difficult terms or concepts faster. The method combines individual reflection with social correction and shared precision.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.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.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
10-20 min je Frage30-60 min45-90 minUp to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
Participantsdifferent
6-503-124-12Scrum Team
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Concept Questions, Vote Results, Learning NotesStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, ExperimentsImprovement actions, Team agreements
Tagsno overlap
LearningDialogueFacilitation
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
RetrospectiveImprovementLearning
Add more methods