methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Bottleneck Analysis.
Operations
Bottleneck Analysis
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Purposedifferent
For a flow that backs up at one point, the method looks for the capacity limit with the greatest leverage. It explains why extra effort elsewhere barely improves throughput.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 should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.
Complexitydifferent
MediumLowLow
Timedifferent
1-3 h45-90 min45–75 min
Participantsdifferent
3-84-12Team members involved
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Bottleneck Map, Flow Metrics, Improvement Options, Follow-up MeasuresSailboat Board, Risks, Improvement Actions4Ls Board, Learning Themes, Improvement Actions
Tagsno overlap
FlowMeasurementConstraints
RetrospectiveTeamImprovement
RetrospectiveLearningReflectionTeam
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective