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 Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration for Delegation Poker.
Facilitation
Delegation Poker
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
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 decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitysame
LowLowLow
Timesame
45-90 min45-90 min45-90 min
Participantsdifferent
4-123-104-12
Formatsame
WorkshopWorkshopWorkshop
Outputdifferent
Starfish Board, Practice Changes, ExperimentsDelegation Board, Decision Boundaries, Role AgreementsSailboat Board, Risks, Improvement Actions
Tags1 shared
RetrospectiveImprovementExperimentsTeam
AutonomyRolesTeam
RetrospectiveTeamImprovement
Add more methods

Often compared together

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

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