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
The Scrum Team inspects people, interactions, processes, tools, and the Definition of Done, then agrees on a few testable improvements.
Agile
Sprint Retrospective
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 Mad Sad Glad
Agile
Mad Sad Glad
Purposedifferent
When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together.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's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible.
Complexitydifferent
LowMediumLowLow
Timedifferent
Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorterOngoing30-60 min30-60 min
Participantsdifferent
Scrum Team2-203-123-10
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Improvement actions, Team agreementsChat Transcript, Action Log, AutomationsStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action Items
Tagsno overlap
RetrospectiveImprovementLearning
CollaborationEngineeringIncident
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Add more methods