Strategic DDD with Big Picture and Process Level Event Storming
This workshop is designed for experienced developers, architects, and analysts who work on large-scale, domain-rich systems. It provides hands-on practice with Big Picture and Process Level Event Storming, a visual, collaborative technique that helps teams rapidly explore complex business domains, uncover risks, align stakeholders, and drive architectural decisions.
Participants will learn how to facilitate strategic conversations using domains, ubiquitous language all foundational patterns in Strategic Domain-Driven Design (DDD) leading to bounded contexts and context maps.
Learning Objectives
Master the Big Picture Event Storming technique to analyze existing or new systems.
Learn and apply strategic DDD patterns: Domains, Ubiquitous Language and also Bounded Context, Context Mapping.
Connect business analysis with architectural and organizational design decisions.
Use artifacts from Event Storming sessions to define teams, services, and system boundaries.
Key Benefits
Practical, step-by-step guidance for facilitating impactful Big Picture and Process Level Event Storming sessions.
Learn how to model and map complex domains collaboratively.
Understand how to make informed architectural and organizational decisions based on strategic patterns.
Develop a shared language across business and tech stakeholders.
Work on a realistic domain scenario from initial chaos to structured, mapped contexts.
Who Should Attend?
Experienced developers, architects, and technical leads.
Business or systems analysts working with complex domains.
Cross-functional teams seeking to define clear domain boundaries and align architecture with business goals.
Prerequisites
Understanding of domain analysis and software architecture
Practicalities
Level: Advanced
Presenter:
I help teams delivering value faster, understanding business needs and building scalable Architecture and Shift-left Testing Strategy. With a passion and trust.
I have the experience, knowledge, passion and open mindset - perfect skills to deliver value to the customers and the businesses with:
✔ Speed - required to catch the market opportunity
✔ Quality - to retain and scale
Proven by:
✔ Building and maintaining systems at the core for the entire business stability
✔ Significantly reducing the cost of manual tests by implementing Shift-left testing strategy
✔ Iteratively designing and building Architecture open for business expansion yet not over-engineered
Agenda – What You’ll Learn and Build
For developers, architects, and analysts shaping the strategic structure of software systems
1. Understanding the Foundations of Event Storming
• What domain events are and how they help model business behavior
• The Event Storming mindset: exploration through collaboration
You’ll gain the ability to use Event Storming as a universal discovery language across disciplines.
2. Facilitating a Successful Session
• What’s needed to run a productive session (tools, space, participants)
• In-person vs. online, how to adapt
• The role of the facilitator in guiding exploration
You'll be equipped to run sessions that produce valuable business and architectural insights.
3. Big Picture Event Storming in Action
• When and why to use Big Picture Event Storming
• Modeling greenfield vs. legacy systems
You’ll learn how to zoom out and explore the system landscape, aligning your team around a common view.
4. Applying Strategic DDD Patterns
• Discovering and using Ubiquitous Language
• Identifying Domains and Ubiquitous Language
• Defining Bounded Contexts and Context Maps to visualize relationships
You’ll use these patterns to draw clear lines between responsibilities, organizationally and technically.
5. Exploring the Domain
• Introduce a realistic business domain scenario
• Apply visual notations and techniques
• Learn Chaotic Exploration and Chronological Structuring
You’ll practice making sense of messy domains by structuring them step-by-step.
6. Defining Bounded Contexts
• Identifying language boundaries and conceptual seams
• Common pitfalls and how to avoid them
You’ll leave with the ability to define clean, autonomous domains that scale with your organization.
7. Designing Cross-Context Communication
• Communication styles and integration patterns between contexts
• Weighing trade-offs: autonomy, coupling, complexity
You’ll make informed decisions about how services should interact based on strategic clarity.
8. From Contexts to Architecture
• Connecting Bounded Contexts to implementation
• Data Model vs. Domain Model, making the right architectural calls
• Mapping contexts to teams, services, and ownership
You’ll learn how to design systems and teams that reflect the shape of the business, not the org chart.
