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 Delegation Poker.
Facilitation
Delegation Poker
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
Paper illustration for Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
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 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 team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min30-60 min45-90 min30-60 min
Participantsdifferent
3-103-124-123-10
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
Delegation Board, Decision Boundaries, Role AgreementsStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, ExperimentsEmotion Board, Themes, Action Items
Tags1 shared
AutonomyRolesTeam
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
RetrospectiveTeamReflection
Add more methods