Model storming - a different approach to collaborative model discovery (Vilnius edition)

avanscoperta

Model
Storming
A diﬀerent approach to
collaborative model discovery
@ziobrando
#buildstuﬄt #modelstorming #eventstorming

About me

About me

@ziobrando

@ziobrando
!

I do something else instead

avanscoperta

About me

About me

@ziobrando

DDD enthusiast

@ziobrando
!


avanscoperta

About me

About me

@ziobrando

DDD enthusiast
@ziobrando
Post-it addicted
!


avanscoperta

About me

About me

@ziobrando

DDD enthusiast
@ziobrando
Post-it addicted
Visual something else instead
I do thinker
!

avanscoperta

About me

About me

@ziobrando

DDD enthusiast
@ziobrando
Post-it addicted
I do thinker
Chaos summoner
!

avanscoperta

About me

About me

@ziobrando

DDD enthusiast
@ziobrando
Post-it addicted
I do thinker
Chaos summoner
Idea thief
!

avanscoperta

About me

About me

@ziobrando

DDD enthusiast
@ziobrando
Post-it addicted
I do thinker
Chaos summoner
Idea thief
…never satisﬁed
avanscoperta
!

Part 1:
My insanely ambitious starting point

Typical enterprise architecture is ﬂawed

pl i
Ap

io n
c at

Ap

pl i

D at a ba se

ca

io n n
t
ca
io
io n
i
pl
at
c at
Ap
l ic
pl i
pp
Ap
A

pp
A

tio

on
ti
ca
li

pl i
Ap

io n
at
c

n

l ic
pp

A

on
ti
a

D at a ba se

Typical enterprise architecture is ﬂawed
© Alberto Brandolini 2013

Some folks call this a “model”

So you want to speak the “Ubiquitous
Language”, you scumbag?

©
Alberto
Brandolini
2009
011

So you want to speak the “Ubiquitous
Language”, you scumbag?

The only ubiquitous language is SQL!
Every Database speaks it!
©
Alberto
Brandolini
2009
011

Managing conﬂicting requirements
is always a pleasure

So we have trade offs


When will we
start refactoring?


When will we
start refactoring?

Mañana!!


Problem checklist
Typical enterprise software architecture is
ﬂawed
Data driven
No bounded contexts

Conﬂicting requirements lead to trade-off
solutions that ultimately clog our system
The ever needed refactoring is always scheduled
for the next week

Principle #1
The fastest way to remove
crap from your system is…


To put NO CRAP
into your system

Paratroopers


Paratroopers

Move towards the
taleban area


Paratroopers

Move towards the
taleban area
But this is Arizona…


Paratroopers

Move towards the
taleban area

Let’s iterate!

But this is Arizona…


There’s nothing
wrong with “embrace
change”, but…

Ignorance is the single
greatest impediment
to throughput.
Dan North
http://dannorth.net/2010/08/30/introducing-deliberate-discovery/

Learning is the
constraint

Dan North
http://dannorth.net/2010/08/30/introducing-deliberate-discovery/

Coding 20cl, learning 20cl,
deciding 20cl, waiting...

Software
development is a
learning process
Working code is a
side eﬀect

Why don’t you
put all of them in the
same room?

A simple
solution
Put

A simple solution
Put all the key stakeholders
in the same room and
sketch a model together


Reasons why this is a bad idea

Too expensive to get all the key people in the
same room at the same time

The meeting will be totally non productive

Disagreement will turn into a ﬁght

The meeting will be boring

They won’t come again

They won’t come again
They’ll blame me

1. Designate a scapegoat
2. Let him call the meeting

©
Alberto
Brandolini
2009

Solution #2
Break some assumptions

Implicit assumptions
The meeting will happen around a table

When one person speaks many will be bored

When many person speak nobody will
understand

understand
We’ll talk about technical things

understand
We’ll talk about technical things
I’ll have to bring my smartphone with me

The challenge
Can we run a meeting worth
more than the hourly cost of
the participants?


Yes, I mean that much
space...

My best friend


It’s no fun to just
watch others play

We’re getting to the
aggregates outside-in

Observe people


Observe people
help those who are not
participating


Observe people
participating
remove impediments and
bottlenecks


Observe people
participating
bottlenecks
Spot the ones who don’t belong
here

Observe people
participating
bottlenecks
here
Spot the ones that care

Observe people
participating
bottlenecks
here
Spot the ones that care
Manage conﬂicts


I love conﬂicts here…

Or we can simply put
a
RED Marker
©
Alberto
Brandolini
2009

There’s nothing
wrong in learning
stuﬀ faster

A little community
Started experimenting


A little community
@mathiasverraes


A little community
@mathiasverraes @heimeshoﬀ


A little community
@andreabalducci


A little community
@andreabalducci
@tojans

A little community
@tjaskula
@andreabalducci
@tojans

A little community
@tjaskula
@andreabalducci
@tojans @yreynhout

A little community
@tjaskula
@andreabalducci
@tojans @yreynhout
@alessandrocolla

A little community
@tjaskula
@andreabalducci
@tojans @yreynhout
@jefclaes
@alessandrocolla

A little community
@tjaskula
@andreabalducci
@tojans @yreynhout
@jefclaes
@alessandrocolla
@lorenzomassacci


A little community
@tjaskula
@andreabalducci
@sleli
@tojans @yreynhout
@jefclaes
@alessandrocolla
@lorenzomassacci


And the experiments
worked!


And the experiments
worked!
“This is awesome!”


And the experiments
worked!
“For the ﬁrst time,
developers started asking
the right questions!”


And the experiments
worked!
“For the ﬁrst time,
developers started asking
the right questions!”

“We turned the model
into implementation on
the same afternoon”


And the experiments
triggered new ideas


And the experiments
triggered new ideas
“Let’s use it to set up our Kanban board!”


And the experiments
triggered new ideas

“is there a UX version
of the workshop?”


And the experiments
triggered new ideas

of the workshop?”

“How can we use this to
steer implementation?”


And the experiments
triggered new ideas
“We used a diﬀerent
set of rules”

of the workshop?”

“How can we use this to
steer implementation?”


Part 4:
Model Storming
or
Meta ﬁshing

What is Model Storming?


Unlimited Modeling Space


Iterative notation


Iterative notation
Simple Gaming Rules


Iterative notation
Simple Gaming Rules
Active Collaboration


Iterative notation
Simple Gaming Rules
Addressing Complexity


Iterative notation
Simple Gaming Rules
Everything is visible

Iterative notation
Simple Gaming Rules
Supporting divergence

Iterative notation
Simple Gaming Rules
Supporting divergence
Decide later


My problem is...


My problem is...

BIGGER

You know why people
call it “the big
picture?”

Guerrilla modeling


Unlimited surface


Unlimited surface
You don’t know the size of the
problem before exploring it


Iterative notation


Iterative notation
Choose one signiﬁcant
aspect


Iterative notation
aspect
Find the simplest possible
notation to represent it


Iterative notation
aspect
Find the simplest possible
notation to represent it
Choose the next aspect to
model

All participant should
actively contribute


One
Man
One
Marker

Tell us whatever you want

Our brain...

http://www.wpclipart.com/medical/anatomy/brain/four_lobes_of_the_cerebral_cortex.png.html

System 1
Quick pattern matching

System 1
Parallel processing, unaware mode

System 1
Low energy consumption

System 1

System 2

System 1

System 2
Complex elaboration that need
attention and concentration

System 1

System 2
No parallelism

System 1

System 2
No parallelism
High energy consumption

Maybe there’s a
reason for that

Let’s examine carefully
every possibility

System 1

System 2
No parallelism

It’s the
same class!

System 1

It’s the
same class!


System 2
No parallelism

It’s obvious!

System 1

It’s the
same class!


System 2
No parallelism

It’s obvious!

Let’s consider
Bounded Contexts

System 1

It’s the
same class!


System 2
No parallelism

It’s obvious!

Let’s consider
Bounded Contexts
Let’s see
the whole

Our brain


Our brain
Quick in pattern matching


Our brain
(and unaware of it)


Our brain
(and unaware of it)
Provides inferior solutions
under pressure


Our brain
(and unaware of it)
under pressure
Tries to avoid complexity


Our brain
(and unaware of it)
under pressure
Tries to avoid complexity
Gets hooked by games

Can you walk by
without completing?

And, by the way, playing
is how we learn better

Deferring decisions
Implicit choices
There’s nothing *right* yet
No legacy


Embrace Fuzzyness
(temporarily)


Data ﬁrst, structure later…

Everybody is
partitioning the
system

I just like taking a
detour ﬁrst...

Visual representation
UML is too complex to
support a meaningful
conversation!
!

Whiteboards won’t compile
anyway

Visualize everything


Visualize everything
Legend and Notation
Requirements and solution
Solutions
Disagreement
Context
...

Design the workshop
User Experience

Exploring
Guys, we’re doing this one
really badly


Brainstorming rules
“We need at least 3 bad
ideas”


Short timeboxes
throwaway code
...more ;-)
coderetreat.org

Human beings are the
best device ever…

…to detect somebody
else’s mistakes

Negotiating
We need a
tangible enemy
if there’s none ...


Your colleague
becomes the enemy

Negotiating
implicit meaning
Blah, blah, blah...

...And
obviously, blah,
blah...

Blah, blah, blah...

Ouch, he didn’t
mention wah, wah...

A tangible artifact
becomes the enemy

Your colleague
becomes your ally

Proving
Still… negotiating is waste
It’s not about convincing the
others...


Watching the ceiling
is forbidden!

Event Storming
expected outcome
steered towards a canonical
model
partially deﬁned steps
model aﬃnity
given problem type

Model storming
unpredictable outcome
no canonical model
notation incremente
iteratively
!

no predeﬁned problem type

Some problems are resistant
to antibiotics

It’s a fun job
and
somebody’s gotta do
it

avanscoperta

Grazie!
@ziobrando
!

http://ziobrando.blogspot.com/2013/11/introducing-event-storming.html
http://www.avanscoperta.it

Model storming - a different approach to collaborative model discovery (Vilnius edition)

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (8)

Andere mochten auch

Andere mochten auch (18)

Ähnlich wie Model storming - a different approach to collaborative model discovery (Vilnius edition)

Ähnlich wie Model storming - a different approach to collaborative model discovery (Vilnius edition) (20)

Mehr von Alberto Brandolini

Mehr von Alberto Brandolini (17)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Model storming - a different approach to collaborative model discovery (Vilnius edition)