EventStorming is a workshop format that enables massive learning on complex business domains and promotes collaboration between different disciplines and across teams.
In this two-day workshop, we’ll practice three different flavours (Big Picture, Process Modelling and Software Design), applied to real-world business problems.
We’ll take into account the different perspectives (including the facilitator) in a process that spans large-scale discovery, to leverage collaborative design.
We’ll experience the how, and we’ll discuss the why.
Who Should Attend
EventStorming is interdisciplinary. The specialistic notation is dropped in favour of an incremental lo-fi notation that allows an inclusive approach, while driving the exploration towards the most sensitive areas. Every participant will actively contribute. Typical roles include Software Architects, Product Owners, Business Analysts and Service Designer, UX expert and more.
What You Will Learn
The goal is to enable participants to understand the principle and mechanics, for running their own workshop and to use EventStorming as a modeling tool to support their design decisions.
Day 1 - Discovery
Kick-off: where are we and where we want to go.
Real world Big Picture EventStorming, mastering complexity and unknowns in largescale modelling
Managing conflicts, highlighting risks, and the problems really worth solving
The facilitator’s toolbox revealed
Improving our process exploring motivations of different actors
The Change agent’s perspective: why it’s going to be hard even when improvement is obvious, and how to deal with stalemates
Everything’s connected: Lean & Kanban, complexity and organisation limits
Working with startups vs. working with established companies
Emerging System Boundaries: from EventStorming to Bounded Contexts
EventStorming as a platform for problem-solving
ModelStorming: modelling everything without a clue (and yet deliver amazing insights)
Day 2 - Collaborative Design
Process Modelling EventStorming: a cross-discipline platform for collaborative modelling
Design around the bottleneck: changing the rules of the game.
Blending User Experience Design and Service Design into Software Design.
Triggering bullet-proof design with visible state.
From sticky notes to working software. When to go for a sophisticated architecture.