Model storming - a different approach to collaborative model discovery (Vilnius edition)
•
41 likes•5,135 views
Many complex problems aren't properly managed because they aren't properly seen. To visualise them you need a lot of space and unusual techniques that help you model the unknown, in an interactive and extremely productive fashion.
Recommended
Recommended
More Related Content
What's hot
What's hot (8)
Viewers also liked
Viewers also liked (18)
Similar to Model storming - a different approach to collaborative model discovery (Vilnius edition)
Similar to Model storming - a different approach to collaborative model discovery (Vilnius edition) (20)
More from Alberto Brandolini
More from Alberto Brandolini (17)
Recently uploaded
Recently uploaded (20)
Model storming - a different approach to collaborative model discovery (Vilnius edition)
- 1. avanscoperta Model Storming A different approach to collaborative model discovery @ziobrando #buildstufflt #modelstorming #eventstorming
- 2. About me About me @ziobrando @ziobrando ! I do something else instead avanscoperta
- 3. About me About me @ziobrando DDD enthusiast @ziobrando ! I do something else instead avanscoperta
- 4. About me About me @ziobrando DDD enthusiast @ziobrando Post-it addicted ! I do something else instead avanscoperta
- 5. About me About me @ziobrando DDD enthusiast @ziobrando Post-it addicted Visual something else instead I do thinker ! avanscoperta
- 6. About me About me @ziobrando DDD enthusiast @ziobrando Post-it addicted Visual something else instead I do thinker Chaos summoner ! avanscoperta
- 7. About me About me @ziobrando DDD enthusiast @ziobrando Post-it addicted Visual something else instead I do thinker Chaos summoner Idea thief ! avanscoperta
- 8. About me About me @ziobrando DDD enthusiast @ziobrando Post-it addicted Visual something else instead I do thinker Chaos summoner Idea thief …never satisfied avanscoperta !
- 9. Part 1: My insanely ambitious starting point
- 10. Typical enterprise architecture is flawed
- 11. 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 flawed © Alberto Brandolini 2013
- 14. Some folks call this a “model”
- 15. So you want to speak the “Ubiquitous Language”, you scumbag? © Alberto Brandolini 2009 011
- 16. So you want to speak the “Ubiquitous Language”, you scumbag? The only ubiquitous language is SQL! Every Database speaks it! © Alberto Brandolini 2009 011
- 17. Managing conflicting requirements is always a pleasure © Alberto Brandolini 2013
- 18. So we have trade offs © Alberto Brandolini 2013
- 19. © Alberto Brandolini 2013
- 20. When will we start refactoring? © Alberto Brandolini 2013
- 21. When will we start refactoring? Mañana!! © Alberto Brandolini 2013
- 22. Problem checklist Typical enterprise software architecture is flawed Data driven No bounded contexts Conflicting requirements lead to trade-off solutions that ultimately clog our system The ever needed refactoring is always scheduled for the next week
- 23. Principle #1 The fastest way to remove crap from your system is… © Alberto Brandolini 2013
- 24. To put NO CRAP into your system
- 25. Paratroopers © Alberto Brandolini 2013
- 26. Paratroopers Move towards the taleban area © Alberto Brandolini 2013
- 27. Paratroopers Move towards the taleban area But this is Arizona… © Alberto Brandolini 2013
- 28. Paratroopers Move towards the taleban area Let’s iterate! But this is Arizona… © Alberto Brandolini 2013
- 29. There’s nothing wrong with “embrace change”, but…
- 31. Ignorance is the single greatest impediment to throughput. Dan North http://dannorth.net/2010/08/30/introducing-deliberate-discovery/
- 32. Learning is the constraint Dan North http://dannorth.net/2010/08/30/introducing-deliberate-discovery/
- 33. Coding 20cl, learning 20cl, deciding 20cl, waiting...
- 35. Software development is a learning process Working code is a side effect
- 37. Part 2: Teach a man to fish
- 38. Why don’t you put all of them in the same room? A simple solution Put
- 39. A simple solution Put all the key stakeholders in the same room and sketch a model together © Alberto Brandolini 2013
- 40. That will never work
- 41. Reasons why this is a bad idea
- 42. Reasons why this is a bad idea Too expensive to get all the key people in the same room at the same time
- 43. 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
- 44. 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 fight
- 45. 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 fight The meeting will be boring
- 46. 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 fight The meeting will be boring They won’t come again
- 47. 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 fight The meeting will be boring They won’t come again They’ll blame me
- 48. Solution #1
- 49. 1. Designate a scapegoat 2. Let him call the meeting © Alberto Brandolini 2009
- 50. Solution #2 Break some assumptions
- 52. Implicit assumptions The meeting will happen around a table
- 53. Implicit assumptions The meeting will happen around a table When one person speaks many will be bored
- 54. Implicit assumptions The meeting will happen around a table When one person speaks many will be bored When many person speak nobody will understand
- 55. Implicit assumptions The meeting will happen around a table When one person speaks many will be bored When many person speak nobody will understand We’ll talk about technical things
- 56. Implicit assumptions The meeting will happen around a table When one person speaks many will be bored When many person speak nobody will understand We’ll talk about technical things I’ll have to bring my smartphone with me
- 57. That’s how I run meetings
- 58. The challenge Can we run a meeting worth more than the hourly cost of the participants? © Alberto Brandolini 2013
- 59. Event Storming!
- 64. © Alberto Brandolini 2013
- 65. Yes, I mean that much space...
- 66. My best friend © Alberto Brandolini 2013
- 67. And… no table.
- 70. It’s no fun to just watch others play
- 75. We’re getting to the aggregates outside-in
- 76. Observe people
- 78. Observe people © Alberto Brandolini 2013
- 79. Observe people help those who are not participating © Alberto Brandolini 2013
- 80. Observe people help those who are not participating remove impediments and bottlenecks © Alberto Brandolini 2013
- 81. Observe people help those who are not participating remove impediments and bottlenecks Spot the ones who don’t belong here © Alberto Brandolini 2013
- 82. Observe people help those who are not participating remove impediments and bottlenecks Spot the ones who don’t belong here Spot the ones that care © Alberto Brandolini 2013
- 83. Observe people help those who are not participating remove impediments and bottlenecks Spot the ones who don’t belong here Spot the ones that care Manage conflicts © Alberto Brandolini 2013
- 84. I love conflicts here… © Alberto Brandolini 2013
- 85. © Alberto Brandolini 2013
- 86. Or we can simply put a RED Marker © Alberto Brandolini 2009
- 87. There’s nothing wrong in learning stuff faster
- 88. This summer…
- 89. A little community Started experimenting © Alberto Brandolini 2013
- 90. A little community Started experimenting @mathiasverraes © Alberto Brandolini 2013
- 91. A little community Started experimenting @mathiasverraes @heimeshoff © Alberto Brandolini 2013
- 92. A little community Started experimenting @mathiasverraes @heimeshoff @andreabalducci © Alberto Brandolini 2013
- 93. A little community Started experimenting @mathiasverraes @heimeshoff @andreabalducci @tojans © Alberto Brandolini 2013
- 94. A little community Started experimenting @mathiasverraes @heimeshoff @tjaskula @andreabalducci @tojans © Alberto Brandolini 2013
- 95. A little community Started experimenting @mathiasverraes @heimeshoff @tjaskula @andreabalducci @tojans @yreynhout © Alberto Brandolini 2013
- 96. A little community Started experimenting @mathiasverraes @heimeshoff @tjaskula @andreabalducci @tojans @yreynhout @alessandrocolla © Alberto Brandolini 2013
- 97. A little community Started experimenting @mathiasverraes @heimeshoff @tjaskula @andreabalducci @tojans @yreynhout @jefclaes @alessandrocolla © Alberto Brandolini 2013
- 98. A little community Started experimenting @mathiasverraes @heimeshoff @tjaskula @andreabalducci @tojans @yreynhout @jefclaes @alessandrocolla @lorenzomassacci © Alberto Brandolini 2013
- 99. A little community Started experimenting @mathiasverraes @heimeshoff @tjaskula @andreabalducci @sleli @tojans @yreynhout @jefclaes @alessandrocolla @lorenzomassacci © Alberto Brandolini 2013
- 100. And the experiments worked! © Alberto Brandolini 2013
- 101. And the experiments worked! “This is awesome!” © Alberto Brandolini 2013
- 102. And the experiments worked! “This is awesome!” “For the first time, developers started asking the right questions!” © Alberto Brandolini 2013
- 103. And the experiments worked! “This is awesome!” “For the first time, developers started asking the right questions!” “We turned the model into implementation on the same afternoon” © Alberto Brandolini 2013
- 104. And the experiments triggered new ideas © Alberto Brandolini 2013
- 105. And the experiments triggered new ideas “Let’s use it to set up our Kanban board!” © Alberto Brandolini 2013
- 106. And the experiments triggered new ideas “Let’s use it to set up our Kanban board!” “is there a UX version of the workshop?” © Alberto Brandolini 2013
- 107. And the experiments triggered new ideas “Let’s use it to set up our Kanban board!” “is there a UX version of the workshop?” “How can we use this to steer implementation?” © Alberto Brandolini 2013
- 108. And the experiments triggered new ideas “Let’s use it to set up our Kanban board!” “We used a different “is there a UX version set of rules” of the workshop?” “How can we use this to steer implementation?” © Alberto Brandolini 2013
- 109. © Alberto Brandolini 2013
- 110. © Alberto Brandolini 2013
- 111. Part 4: Model Storming or Meta fishing
- 112. I know, Part 3 is missing…
- 113. Why does this work?
- 114. My secret weapon?
- 115. My secret weapon?
- 116. What is Model Storming? © Alberto Brandolini 2013
- 117. What is Model Storming? Unlimited Modeling Space © Alberto Brandolini 2013
- 118. What is Model Storming? Unlimited Modeling Space Iterative notation © Alberto Brandolini 2013
- 119. What is Model Storming? Unlimited Modeling Space Iterative notation Simple Gaming Rules © Alberto Brandolini 2013
- 120. What is Model Storming? Unlimited Modeling Space Iterative notation Simple Gaming Rules Active Collaboration © Alberto Brandolini 2013
- 121. What is Model Storming? Unlimited Modeling Space Iterative notation Simple Gaming Rules Active Collaboration Addressing Complexity © Alberto Brandolini 2013
- 122. What is Model Storming? Unlimited Modeling Space Iterative notation Simple Gaming Rules Active Collaboration Addressing Complexity Everything is visible © Alberto Brandolini 2013
- 123. What is Model Storming? Unlimited Modeling Space Iterative notation Simple Gaming Rules Active Collaboration Addressing Complexity Everything is visible Supporting divergence © Alberto Brandolini 2013
- 124. What is Model Storming? Unlimited Modeling Space Iterative notation Simple Gaming Rules Active Collaboration Addressing Complexity Everything is visible Supporting divergence Decide later © Alberto Brandolini 2013
- 125. Unlimited Modeling Space My problem is... © Alberto Brandolini 2013
- 126. Unlimited Modeling Space My problem is... BIGGER © Alberto Brandolini 2013
- 127. You know why people call it “the big picture?”
- 129. Guerrilla modeling © Alberto Brandolini 2013
- 130. © Alberto Brandolini 2013
- 131. Unlimited surface © Alberto Brandolini 2013
- 132. Unlimited surface You don’t know the size of the problem before exploring it © Alberto Brandolini 2013
- 133. Iterative notation © Alberto Brandolini 2013
- 134. Iterative notation Choose one significant aspect © Alberto Brandolini 2013
- 135. Iterative notation Choose one significant aspect Find the simplest possible notation to represent it © Alberto Brandolini 2013
- 136. Iterative notation Choose one significant aspect Find the simplest possible notation to represent it Choose the next aspect to model © Alberto Brandolini 2013
- 137. Active Collaboration All participant should actively contribute © Alberto Brandolini 2013
- 138. One Man One Marker © Alberto Brandolini 2013
- 139. © Alberto Brandolini 2013
- 140. Tell us whatever you want © Alberto Brandolini 2013
- 141. Gamification!
- 142. © Alberto Brandolini 2013
- 145. System 1
- 146. System 1 Quick pattern matching
- 147. System 1 Quick pattern matching Parallel processing, unaware mode
- 148. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption
- 149. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption System 2
- 150. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration
- 151. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism
- 152. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism High energy consumption
- 153. Maybe there’s a reason for that
- 154. Let’s examine carefully every possibility
- 156. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism High energy consumption
- 157. System 1 Quick pattern matching Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism High energy consumption It’s the same class!
- 158. System 1 Quick pattern matching It’s the same class! Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism High energy consumption It’s obvious!
- 159. System 1 Quick pattern matching It’s the same class! Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism High energy consumption It’s obvious! Let’s consider Bounded Contexts
- 160. System 1 Quick pattern matching It’s the same class! Parallel processing, unaware mode Low energy consumption System 2 Complex elaboration that need attention and concentration No parallelism High energy consumption It’s obvious! Let’s consider Bounded Contexts Let’s see the whole
- 161. Our brain © Alberto Brandolini 2013
- 162. Our brain Quick in pattern matching © Alberto Brandolini 2013
- 163. Our brain Quick in pattern matching (and unaware of it) © Alberto Brandolini 2013
- 164. Our brain Quick in pattern matching (and unaware of it) Provides inferior solutions under pressure © Alberto Brandolini 2013
- 165. Our brain Quick in pattern matching (and unaware of it) Provides inferior solutions under pressure Tries to avoid complexity © Alberto Brandolini 2013
- 166. Our brain Quick in pattern matching (and unaware of it) Provides inferior solutions under pressure Tries to avoid complexity Gets hooked by games © Alberto Brandolini 2013
- 167. © Alberto Brandolini 2013
- 168. © Alberto Brandolini 2013
- 169. Can you walk by without completing? © Alberto Brandolini 2013
- 170. © Alberto Brandolini 2013
- 171. And, by the way, playing is how we learn better © Alberto Brandolini 2013
- 172. Icebreakers needed
- 173. Deferring decisions Implicit choices There’s nothing *right* yet No legacy © Alberto Brandolini 2013
- 175. It will compile
- 176. I promise
- 177. © Alberto Brandolini 2013
- 178. Addressing Complexity Data first, structure later…
- 180. I just like taking a detour first...
- 181. Visual representation UML is too complex to support a meaningful conversation! ! Whiteboards won’t compile anyway © Alberto Brandolini 2013
- 182. Visualize everything © Alberto Brandolini 2013
- 183. © Alberto Brandolini 2013
- 184. © Alberto Brandolini 2013
- 185. Visualize everything Legend and Notation Requirements and solution Solutions Disagreement Context ... © Alberto Brandolini 2013
- 186. Keep the cognitive load small
- 187. Design the workshop User Experience
- 188. Exploring Guys, we’re doing this one really badly © Alberto Brandolini 2013
- 189. Brainstorming rules “We need at least 3 bad ideas” © Alberto Brandolini 2013
- 190. Short timeboxes throwaway code ...more ;-) coderetreat.org
- 191. coderetreat.org
- 192. coderetreat.org
- 193. coderetreat.org
- 194. coderetreat.org
- 195. coderetreat.org
- 196. coderetreat.org
- 197. coderetreat.org
- 198. coderetreat.org
- 199. Can we tweak it?
- 200. Modellathlon!
- 201. Human beings are the best device ever…
- 202. …to detect somebody else’s mistakes
- 203. Negotiating We need a tangible enemy if there’s none ... © Alberto Brandolini 2013
- 204. Your colleague becomes the enemy
- 205. Negotiating implicit meaning Blah, blah, blah... ...And obviously, blah, blah... Blah, blah, blah... Ouch, he didn’t mention wah, wah... © Alberto Brandolini 2013
- 206. A tangible artifact becomes the enemy
- 207. Your colleague becomes your ally
- 208. Proving Still… negotiating is waste It’s not about convincing the others... © Alberto Brandolini 2013
- 213. Watching the ceiling is forbidden!
- 214. Scope?
- 215. Complex problems
- 216. Event Storming expected outcome steered towards a canonical model partially defined steps model affinity given problem type © Alberto Brandolini 2013
- 217. Model storming unpredictable outcome no canonical model notation incremente iteratively ! no predefined problem type © Alberto Brandolini 2013
- 218. © Alberto Brandolini 2013
- 219. © Alberto Brandolini 2013
- 221. Some problems are resistant to antibiotics
- 222. It’s a fun job and somebody’s gotta do it
- 223. Let’s go fishing!