DOMINE O EVENT STORMING!

Summary

In this video, the host dives deep into the Event Storming technique, a collaborative workshop aimed at transforming business knowledge into actionable software development insights. Originated by Alberto Brandolini, it's a method to bridge the gap between business and technical experts. The host explains the process, from initial setup to detailed steps like event collection, refinement, cause identification, and reclassification, using sticky notes for visual representation. The goal is to model complex business processes simply, making it easier for developers to understand and implement solutions. The summary also includes a real-world application example, emphasizing the technique's practicality and effectiveness in software design.

Takeaways

• 😀 The video is about an in-depth discussion on Event Storming, a technique for modeling software systems by understanding business events.
• 🌟 Event Storming was created by Alberto Brandolini to bridge the gap between business knowledge and software developers' implementation.
• 💡 The method emphasizes the importance of a common language for all stakeholders to ensure everyone has a clear understanding of the business domain and its requirements.
• 👥 Event Storming is a collaborative workshop involving 6 to 10 participants, including domain experts, developers, and a facilitator.
• 🕒 The preparation for an Event Storming session takes about 20 minutes, and the session itself should last between 3 to 6 hours.
• 📝 The process starts with a 'Big Picture' where all domain events are collected using post-it notes, representing different aspects of the business.
• 🔍 After the initial collection, a refinement phase ensures that events are in chronological order, duplicates are removed, and all events make sense in the context of the business.
• 🔑 Identifying causes is crucial, which can be user actions, external systems, time, or automatic reactions, and these are represented visually during the session.
• 🏗️ The 'reclassification' phase organizes the information gathered, identifying aggregates, bounded contexts, and user interfaces, which are essential for software modeling.
• 📈 Event Storming helps in creating a visual model that can be used to understand business processes and can guide the development of software solutions.
• 🤔 The video script also suggests that there are challenges in conducting Event Storming sessions due to the complexity and the need for diverse expertise, but once mastered, it becomes a powerful tool.

Q & A

What is the main topic discussed in the video script?

The main topic discussed in the video script is Event Storming, a collaborative workshop method used in software development to model business processes and domain events.

Who created the Event Storming technique?

The Event Storming technique was created by Alberto Brandolini, an Italian software developer.

Why was Event Storming developed?

Event Storming was developed to address the challenge of transforming business knowledge into software implementation, as there was a significant difficulty in understanding client problems and translating them into software solutions.

What is the ideal number of participants for an Event Storming session?

The ideal number of participants for an Event Storming session is between 6 and 10 people.

How long does the preparation for an Event Storming session typically take?

The preparation for an Event Storming session typically takes around 20 minutes.

What is the recommended duration for an Event Storming session?

The recommended duration for an Event Storming session is between 3 to 6 hours.

Who are the main types of people involved in an Event Storming session?

The main types of people involved in an Event Storming session are technical people (developers, testers), domain experts (people with in-depth knowledge of the business domain), and a facilitator.

What are the four main causes that generate events in Event Storming?

The four main causes that generate events in Event Storming are user actions, external systems, time, and automatic reactions.

What is the purpose of using post-it notes of different colors in Event Storming?

In Event Storming, different colors of post-it notes represent different elements, such as domain events (usually orange), commands (yellow for actors and light yellow for aggregates), external systems (pink), and business processes.