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
Paper illustration for Bucket System.
Agile
Bucket System
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration for Affinity Estimation.
Agile
Affinity Estimation
Purposedifferent
When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.When many tasks need to be classified quickly, it sorts them by perceived effort and similarity. It reduces the effort of fine-grained estimation for large volumes.
Complexitysame
MediumMediumMediumMedium
Timedifferent
30-90 min2-6 h2-8 h30-90 min
Participantsdifferent
3-122-85-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Bucketed Backlog, Relative Estimates, Split CandidatesEvent Model, UI Flow, Commands, Read ModelsEvent Timeline, Ubiquitous Language, Boundaries, Open QuestionsAffinity Size Map, Grouped Estimates, Unclear Items
Tagsno overlap
EstimationBacklogRelative sizing
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignEventsDiscoveryWorkshop
EstimationBacklogRelative sizing
Add more methods