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 Start Stop Continue |  DevOps Incident Timeline Analysis |  Agile Sailboat Retrospective |
|---|---|---|---|
Purposedifferent | 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. | For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable. | 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. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 30-60 min | 60-180 min | 45-90 min |
Participantsdifferent | 3-12 | 3-10 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Incident Timeline, Evidence Log, Delay Analysis, Improvement Actions | Sailboat Board, Risks, Improvement Actions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | IncidentTimelineSite Reliability Engineering | RetrospectiveTeamImprovement |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
