View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Team Charter |  DevOps Blameless Postmortem |  Agile Sailboat Retrospective |  Agile Sprint Retrospective |
|---|---|---|---|---|
Purposedifferent | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. | 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 | Medium | Low | Low |
Timedifferent | 2-4 h | 30-90 min | 45-90 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter |
Participantsdifferent | 3-12 | 3-12 | 4-12 | Scrum Team |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Team Charter, Working Norms, Role Notes | Postmortem Doc, Action Items, Timeline | Sailboat Board, Risks, Improvement Actions | Improvement actions, Team agreements |
Tagsno overlap | TeamAlignmentCollaboration | Site Reliability EngineeringIncidentLearningReliability | RetrospectiveTeamImprovement | RetrospectiveImprovementLearning |