Event Storming Facilitator FAQs

Question 1

Can this skill generate actual implementation code?

Accepted Answer

No, this skill is designed for the modeling phase. Once the domain is modeled, you should use related skills like microservices-architect or spring-boot-engineer to generate the implementation.

Question 2

What are the three levels of facilitation covered?

Accepted Answer

The skill facilitates Level 1: Big Picture (exploring the whole domain), Level 2: Process Level (adding commands and actors), and Level 3: Design Level (identifying aggregates and APIs).

Question 3

Who should be involved in an Event Storming session?

Accepted Answer

Successful sessions require a mix of domain experts who understand the business rules and developers who understand the technical landscape, typically 6-10 people total.

Question 4

What is the primary goal of the Event Storming skill?

Accepted Answer

The primary goal is to help teams discover the business domain, identify bounded contexts, and define system boundaries through a collaborative workshop format before any code is written.

Question 5

How does this skill handle disagreements in business logic?

Accepted Answer

It uses 'Red Hotspots' to mark areas where experts disagree or the language is inconsistent, allowing the team to move forward and resolve specific conflicts later.

Event Storming Facilitator

Key Features

Use Cases

Event Storming Facilitator

Key Features

Use Cases