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 Sprint Retrospective |
|---|---|---|
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 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 | Medium | Low |
Timedifferent | 1-4 Wochen je Sprint, laufend | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-10 (Scrum Team) | Scrum Team |
Formatdifferent | Workshop + async | Workshop |
Outputdifferent | Product Backlog, Sprint Backlog, Increment, Sprint Goal | Improvement actions, Team agreements |
Tagsno overlap | AgileIterationCadence | RetrospectiveImprovementLearning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
