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 Learning Review.
Operations
Learning Review
Paper illustration for Sailboat Retrospective
Agile
Sailboat Retrospective
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.After a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.When a team wants to read momentum, brakes, and risks together, it offers an easily understandable picture of the situation. It makes drive, obstacles, and headwind visible in the same picture.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h30-60 min1-3 h45-90 min
Participantsdifferent
3-83-123-104-12
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesStart Stop Continue Board, Improvement ActionsLearning Review Notes, System Factors, Improvement ActionsSailboat Board, Risks, Improvement Actions
Tagsno overlap
Domain-Driven DesignBoundariesModeling
RetrospectiveImprovementTeamReflection
LearningRetrospectiveIncidentOperations
RetrospectiveTeamImprovement
Add more methods