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 Scrum |  Agile Starfish Retrospective |  Agile Start Stop Continue |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | When a team needs to work in a fixed delivery rhythm, it stabilizes cadence, responsibility, and feedback loops. It makes collaboration reliable across sprint boundaries. | 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 wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | 45-90 min | 30-60 min | 2-5 min je Item |
Participantsdifferent | 3-10 (Scrum Team) | 4-12 | 3-12 | 3-9 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Starfish Board, Practice Changes, Experiments | Start Stop Continue Board, Improvement Actions | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | AgileIterationCadence | RetrospectiveImprovementExperimentsTeam | RetrospectiveImprovementTeamReflection | EstimationAgileRelative sizingTeam |