The sweet spot
•
13 likes•4,419 views
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.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (8)
Similar to The sweet spot
Similar to The sweet spot (20)
Recently uploaded
Recently uploaded (20)
The sweet spot
- 1. Alberto Brandolini avanscoperta @ziobrando The sweet spot
- 2. The start What’s the problem we’re trying to solve?
- 5. The asteroid
- 7. Why?
- 10. Microscope view
- 11. Microscope view
- 12. Microscope view
- 13. Microscope view
- 14. Microscope view new hire
- 15. Microscope view new hire new hire
- 16. Microscope view new hire new hire
- 17. Microscope view new hire new hire
- 18. Microscope view new hire new hire
- 19. Microscope view new hire new hire
- 20. Microscope view new hire new hire
- 21. Microscope view new hire new hire
- 22. Microscope view Department boundary new hire new hire
- 23. Requirements Gathering Yep, that’s a common name for our problem
- 24. How do we collect requirements?
- 29. way too late…
- 30. A simple solution Put all the key stakeholders in the same room and sketch a model together
- 31. Event Storming!
- 32. Not this way
- 35. This is way better
- 38. Active Collaboration All participant should actively contribute
- 39. One Man One Marker
- 40. Chaotic eats sequential for breakfast
- 41. and with a few tricks…
- 43. We basically made the business problem less boring
- 45. It’s not about being faster That’s still thinking linearly
- 47. What’s Eventstorming It’s an act of
- 48. What’s Eventstorming It’s an act of deliberate
- 49. What’s Eventstorming It’s an act of deliberate collective
- 50. What’s Eventstorming It’s an act of deliberate collective learning
- 51. We discover a lot
- 52. Things we swept under the carpet
- 53. The Big Picture All the business process(es) end-to-end and beyond!
- 54. Unlimited Modelling Space My problem is...
- 55. Unlimited Modelling Space My problem is... BIGGER
- 57. Once you see it…
- 58. Conquer first Divide later
- 61. Unlimited surface You don’t know the size of the problem before exploring it
- 62. 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) -...
- 63. In EventStorming -All key stakeholders in the same room -With an unlimited modelling surface -Modelling key processes starting from Domain Events
- 64. Domain Events Sometimes I do things for a reason
- 66. along a timeline
- 72. Can’t you do the same with an activity diagram?
- 73. Of course!
- 75. too afraid of the conference code of conduct to tell the joke
- 76. too afraid of the conference code of conduct to tell the joke Could you please laugh anyway?
- 78. instead…
- 79. Humans evolved as the most efficient creatures to spot someone else’s mistakes
- 80. Let’s use that!
- 81. Business conversation Technical conversation
- 82. Observe Language Interaction Body Language
- 87. We have a big a behavioural model of the whole thing, now what?
- 89. Business conversation Domain-‐Driven Design Event Sourcing CQRS Event Driven Architecture a business-‐driven model evolution
- 90. Adding some DDD spices I lied: we do a little more than just putting everybody in the same room
- 91. Myth N°1: Ubiquitous Language Everybody should speak the same language
- 93. While… Sales Delivery Operations Finance HR
- 94. That looks like
- 96. Or worse! Sales Delivery Operations Finance HR IT
- 97. Trying to reach an agreement is waste
- 98. Mapping disagreement is way more interesting
- 100. Myth N°2: Domain Expert Domain Expert knows it all
- 101. Domain Expert?
- 105. …but they won’t admit it easily
- 106. Modelling Sympathy Don’t know what it means but sounds so cool
- 107. Simple as that
- 108. Aggregates Workshop Participant added Participant removed Add participant Remove participant Maximum Capacity reached
- 110. Commands Add Item to cart Customer Article Details
- 111. UI Constraints Projection Item page (read model) Command User Price Special offer!
- 112. Processes Ticket bought Welcome process Send welcome e-mail
- 113. External Systems Thermometer Temperature registered
- 114. External Systems Command External System
- 115. Design Level Active collaboration Wisdom of the crowd Visually consistent models Big $ visible
- 118. If you don’t I mean I am it! gonna find where you live!
- 119. Business conversation Value Stream / Value creation Interest areas Conflict areas Bottleneck Accidental complexity
- 120. Bottleneck $ Pain Points Do we really need to measure it?
- 121. Backlog Do we really need that?
- 122. Value Creation Network Finally visible (dysfunctions included)
- 124. Pain-Oriented EventStorming Focus on Explore normally foggy areas Let an action plan emerge! Pain Point Someone else’s pain point
- 125. Pain Oriented Show the whole flow Display the pain Explore Choose Event Pain Point
- 126. Danger Zone
- 127. best advice comes from
- 128. best advice comes from KEEP YOUR MOUTH SHUT
- 129. but please…
- 130. Impact Mapping What is the expected outcome?
- 132. POES as retrospective background Big Picture first Retrospective scope explicitly widened Facilitated root cause analysis Hints for collaboration
- 134. As a learning tool Every new hire in avanscoperta gets an EventStorming session The result is visible on the wall … I am here! :-)
- 135. Maximise Learning?
- 136. EventStorming as a Learning Tool
- 137. EventStorming as an experiment planner
- 138. Many others are pointing here… -Lean Startup -Lean UX -Popcorn Flow -Small Controlled Experiments -Modellathlon
- 140. Business experiments Implementation experiments
- 141. Wrapping up Better Learning Better Connections Better Models Playground for experiments Architectural Change Organisational Change … Model Storming?
- 143. References http://ziobrando.blogspot.com #eventstormers su Google+: https://plus.google.com/u/0/
- 144. avanscoperta