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 Working Agreements.
Agile
Working Agreements
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
Purposedifferent
When collaboration needs more than implicit expectations, it lays out shared ground rules openly. It creates reliability for conduct, availability, and decision paths.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 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
LowMediumLowLow
Timedifferent
45-90 minOngoing30-60 min45-90 min
Participantsdifferent
3-122-203-124-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Working Agreements, Team Norms, Review CadenceChat Transcript, Action Log, AutomationsStart Stop Continue Board, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
TeamCollaborationAgile
CollaborationEngineeringIncident
RetrospectiveImprovementTeamReflection
RetrospectiveTeamImprovement
Add more methods