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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper illustration for Starfish Retrospective
Agile
Starfish Retrospective
Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.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 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.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.
Complexitydifferent
MediumMediumLowLow
Timedifferent
1-3 h1-3 h45-90 min30-60 min
Participantsdifferent
3-82-84-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary NotesStarfish Board, Practice Changes, ExperimentsStart Stop Continue Board, Improvement Actions
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
RetrospectiveImprovementExperimentsTeam
RetrospectiveImprovementTeamReflection
Add more methods