View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  DevOps ChatOps |  Agile Start Stop Continue |  Growth A/B Testing |  Agile Starfish Retrospective |
|---|---|---|---|---|
Purposedifferent | For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together. | 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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. | 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 | High | Low |
Timedifferent | Ongoing | 30-60 min | 1-4 Wochen | 45-90 min |
Participantsdifferent | 2-20 | 3-12 | 1-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop |
Outputdifferent | Chat Transcript, Action Log, Automations | Start Stop Continue Board, Improvement Actions | Experiment results, Decision log, Learning summary | Starfish Board, Practice Changes, Experiments |
Tagsno overlap | CollaborationEngineeringIncident | RetrospectiveImprovementTeamReflection | ExperimentsGrowthAnalyticsValidation | RetrospectiveImprovementExperimentsTeam |