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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 Starfish Retrospective
Agile
Starfish Retrospective
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.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 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
MediumLowLow
Timedifferent
1-3 h30-60 min45-90 min
Participantsdifferent
2-83-124-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesStart Stop Continue Board, Improvement ActionsStarfish Board, Practice Changes, Experiments
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
RetrospectiveImprovementTeamReflection
RetrospectiveImprovementExperimentsTeam
Add more methods

Often compared together

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

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
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas