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
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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
1-3 h30-60 min30-60 min1-3 h
Participantsdifferent
3-83-123-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesStart Stop Continue Board, Improvement ActionsEmotion Board, Themes, Action ItemsContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignBoundariesModeling
RetrospectiveImprovementTeamReflection
RetrospectiveTeamReflection
Domain-Driven DesignBoundariesStrategy
Add more methods