Model Storming

Get Started. It's Free
or sign up with your email address
Rocket clouds
Model Storming by Mind Map: Model Storming

1. Foundations

1.1. Getting to Yes

1.1.1. Actively working to avoid adversarial positions

1.2. Agile Software Development the cooperative game

1.2.1. information radiators

1.2.2. Efficient comunication

1.2.3. Face-to-face conversation mediated by a tool

1.3. Visual Meetings

1.3.1. provide a concrete artifact for understanding

1.3.2. have everybody's ideas displayed

1.4. Agile Modeling

1.5. Cynefin Framework

2. Influencers

2.1. Jurgen Appelo

2.1.1. "Just do it, dude" attitude.

2.2. Olaf Lewitz

2.3. Jeff Patton

2.3.1. Story Mapping

2.4. Esther Derby

2.4.1. Agile Retrospectives

2.5. Dave Gray

2.5.1. Game Storming

2.5.1.1. Simple rules

2.5.1.2. managing divergence & convergence

3. Event Storming

3.1. Influencers

3.1.1. Greg Young

3.1.1.1. Event Sourcing

3.1.1.2. Lambda vs Pi calculus

3.1.1.3. CQRS

3.1.1.4. Model affinity

3.1.1.5. Domain Events

3.1.2. Dan North

3.1.2.1. Deliberate discovery

3.1.2.2. Behavior Driven Development

3.1.3. Gojko Adzic

3.1.3.1. Bridging the communication gap

3.1.3.1.1. Specification Workshops

3.1.3.2. Specification by Example

3.1.4. Udi Dahan

3.1.4.1. Collaborative discovery of Bounded Contexts

3.1.5. Eric Evans

3.1.5.1. Domain-Driven Design

3.1.5.1.1. Bounded Contexts

3.1.5.1.2. Aggregates

3.1.5.1.3. Subdomains

3.1.5.2. Whirlpool Model

3.1.5.3. Brainstorming tips

4. Modellathlon

4.1. Corey Haines

4.1.1. Coderetreat

5. Principles

5.1. Iterative & Emerging notation

5.2. Enforce parallelism

5.3. Read Body language