View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Agile Starfish Retrospective |
|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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. |
Complexitydifferent | Medium | Low |
Timedifferent | Ongoing | 45-90 min |
Participantsdifferent | 2-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | FlowVisual managementDelivery | RetrospectiveImprovementExperimentsTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
