Embed Size (px)
DESCRIPTION
Put the key stakeholders in the same room with an unlimited modelling surface, and some tricks, and you'll end up not only with a viable model, but also with skeleton for continuous improvement.
Citation preview
The sweet spot
@ziobrandoavanscopertaAlberto Brandolini
The startWhat’s the problem we’re
trying to solve?
primordial soup
Then dinosaurs
The asteroid
Organisational silos
Why?
Microscope view
Microscope view
Microscope view
Microscope view
Microscope view
Microscope view
Microscope view
new hire
Microscope view
new hire new hire
Microscope view
new hire new hire
Microscope view
new hire new hire
Microscope view
new hire new hire
Microscope view
new hire new hire
Microscope view
new hire new hire
Microscope view
new hire new hire
Microscope view
new hire new hireDepartment boundary
Requirements Gathering
Yep, that’s a common name for our problem
How do we collect requirements?
Sequential strategyTime...
way too late…
A simple solution
Put all the key stakeholders in the same room and
sketch a model together
Event Storming!
Not this way
This is way better
Sequential gatheringTime…
EventStormingTime…
Active Collaboration
All participant should actively contribute
One Man
One Marker
Chaotic eats sequential for
breakfast
and with a few tricks…
STOP Modelling NOW!!!
We basically made the business problem
less boring
It’s not about being faster
That’s still thinking linearly
What’s Eventstorming
What’s Eventstorming
It’s an act of
What’s Eventstorming
It’s an act of
deliberate
What’s Eventstorming
It’s an act of
deliberate
collective
What’s Eventstorming
It’s an act of
deliberate
collective
learning
We discover a lot
Things we swept under the carpet
The Big Picture
All the business process(es) end-to-end and beyond!
Unlimited Modelling Space
My problem is...
Unlimited Modelling Space
My problem is...
BIGGER
Guerrilla modeling
Once you see it…
Conquer first Divide later
Unlimited surface
Unlimited surfaceYou don’t know the size of the
problem before exploring it
Big Picture approaches-Impact Mapping -> Gojko Adzic
-Specification Workshop -> Gojko Adzic
-User Story Mapping -> Jeff Patton
-Value Stream Mapping -> Stephen Parry (and others, of course)
-...
In EventStorming
-All key stakeholders in the same room
-With an unlimited modelling surface
-Modelling key processes starting from Domain Events
Domain EventsSometimes I do things for a reason
along a timeline
Capture spontaneous complexity
Can’t you do the same with an activity
diagram?
Of course!
too afraid of the conference code of conduct to tell the joke
too afraid of the conference code of conduct to tell the joke
Could you please laugh anyway?
instead…
Humans evolved as the most efficient
creatures to spot someone
else’s mistakes
Let’s use that!
Business conversation
Technical conversation
Observe
Language Interaction
Body Language
We have a big a behavioural model of the whole thing, now
what?
Business conversation
Domain-‐Driven Design Event Sourcing
CQRS Event Driven Architecture
a business-‐driven model evolution
Adding some DDD spices
I lied: we do a little more than just putting everybody in the same room
Myth N°1: Ubiquitous Language
Everybody should speak the same language
Age of aquarius!!!
While…
SalesDelivery
Operations
Finance
HR
That looks like
…that looks like…
Or worse!
SalesDelivery
Operations
Finance
HR
IT
Trying to reach an agreement is waste
Mapping disagreement is way
more interesting
Myth N°2: Domain Expert
Domain Expert knows it all
Domain Expert?
…but they won’t admit it easily
Modelling Sympathy
Don’t know what it means but sounds so cool
Simple as that
Aggregates
Workshop
Participant added
Participant removed
Add participant
Remove participant
Maximum Capacity reached
CommandsAdd Item to cart
Customer
Article Details
UI Constraints
Item pageProjection(read model)
Command
UserPrice
Special offer!
Processes
Ticket bought
Welcome process
Send welcome e-mail
External Systems
Thermometer Temperature registered
External Systems
Command External System
Design Level
Active collaboration Wisdom of the crowd
Visually consistent models Big $ visible
I mean it!
If you don’t I am gonna
find where you live!
Business conversationValue Stream / Value creation
Interest areas Conflict areas
Bottleneck Accidental complexity
Bottleneck $ Pain Points
Do we really need to measure it?
Backlog
Do we really need that?
Value Creation Network
Finally visible (dysfunctions included)
Pain-Oriented EventStorming
Focus on
Explore normally foggy areas
Let an action plan emerge!
Pain Point
Someone else’s pain point
Pain Oriented
Show the whole flow Display the pain Explore Choose
Event
Pain Point
Danger Zone
best advice comes from
best advice comes from
KEEP YOUR
MOUTH SHUT
but please…
Impact Mapping
What is the expected outcome?
Backward implementation
POES as retrospective background
Big Picture first Retrospective scope explicitly
widened Facilitated root cause analysis
Hints for collaboration
As a learning toolEvery new hire in avanscoperta gets an EventStorming session
The result is visible on the wall …
I am here! :-)
Maximise Learning?
EventStorming as a Learning Tool
EventStorming as an experiment planner
Many others are pointing here…
-Lean Startup
-Lean UX
-Popcorn Flow
-Small Controlled Experiments
-Modellathlon
http://www.noop.nl/wp-content/uploads/2014/07/celebration-zone-color.png
Business experiments
Implementation experiments
Wrapping up
Better Learning Better Connections
Better Models Playground for experiments
Architectural Change Organisational Change
… Model Storming?
References
http://ziobrando.blogspot.com #eventstormers su Google+:
https://plus.google.com/u/0/
avanscoperta
Thanks@ziobrando
avanscoperta
