View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Agile Working Agreements | ![]() Agile Start Stop Continue | ![]() Agile Starfish Retrospective | ![]() Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths. | 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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 45-90 min | 2-5 min je Item |
Participantsdifferent | 3-12 | 3-12 | 4-12 | 3-9 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Working Agreements, Team Norms, Review Cadence | Start Stop Continue Board, Improvement Actions | Starfish Board, Practice Changes, Experiments | Relative Estimates, Assumption Notes, Split Candidates |
Tags1 shared | TeamCollaborationAgile | RetrospectiveImprovementTeamReflection | RetrospectiveImprovementExperimentsTeam | EstimationAgileRelative sizingTeam |



