Event Storming
Event Storming is a software design method that enables a team to quickly and interactively understand complex business processes and application requirements.
Ideal for teams that…
Solid backend and architecture — patterns proven in production.
Business process modeling techniques: participants will learn how to model complex business processes effectively using Event Storming, helping them better understand how the organization operates
Creative problem solving: Event Storming requires active participation and team collaboration, which encourages creative thinking and joint problem solving
Understanding customer needs: by diving deeper into business processes, participants will gain a better understanding of client needs and expectations, resulting in products and services that better fit those needs
Designing flexible system architecture: Event Storming can help participants design more flexible and scalable system architectures that can adapt more easily to changing business requirements
What we actually do
- · Introduction to Event Storming What is an event? Different types of events Event Storming as a domain discovery technique
- · How to prepare for a workshop Organizing the session Participants Differences between offline and online sessions
- · Types of workshops Purpose of a workshop Legend (notation) Participants
- · The Role of the Facilitator Responsibilities How to ensure good session dynamics Ensuring quality of discussion Problems and challenges
- · Introduction to the domain used during the workshops
- · Big Picture Event Storming Exploring and getting to know the domain Defining subdomain boundaries Problems and pitfalls
- · Strategic Domain-Driven Design Ubiquitous Language Bounded Context
- · Process Level Organizing and validating the process Enriching the gained knowledge Enhancing the legend
- · Design Level (optional) Adding invariants Adding data Identifying aggregates
- · Event Storming and Project Management Defining tasks based on Event Storming workshops Visualizing risks and ways to deal with them How to handle “Hot Spots”
- · Summary
From brief to retro in 30 days.
Brief & diagnosis
A call with the team lead + a short survey for participants. We define goals, gap and context.
Program customization
We adapt modules, case studies and code examples to your stack. Approval in 5 days.
Workshop
Trainer-led sessions, hands-on, code review. Mentor available between sessions too.
Retro + report
Outcome report for the team and lead. 30 days of consulting included.
Send a brief. We'll reply within 1 day.
After a short brief we'll prepare a program and a quote. No obligations — it's just a starting point.
Thank you!
We'll get back to you within 1 business day.
Other programs for teams
See all →Application architecture
Solid backend and architecture — patterns proven in production.
DDD
Solid backend and architecture — patterns proven in production.
Design patterns in C#
Solid backend and architecture — patterns proven in production.