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 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 Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
LowMedium
Timedifferent
45–75 min1-3 h
Participantsdifferent
Team members involved3-10
Formatsame
WorkshopWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
RetrospectiveLearningReflectionTeam
Domain-Driven DesignContextBoundaries
Add more methods

Often compared together

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

Paper illustration of a team retrospective with three separate Start, Stop, and Continue areas and a shared action list.
Agile
Start Stop Continue
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