Download as PDF, PPTX
![Investigate Policies
How is our system supposed to react to given events?
Whenever [Event] then [Command]
“We need a lilac between the orange and the blue”
Policy](https://image.slidesharecdn.com/softwaredesignasacooperativegamewitheventstorming-191028114043/75/Software-design-as-a-cooperative-game-with-EventStorming-32-2048.jpg)
Uploaded byAlberto Brandolini
Software design as a cooperative game with EventStorming
The document discusses the practice of software design through collaborative techniques like event storming to foster consensus and understanding among stakeholders. It emphasizes the importance of visualizing the entire process, engaging diverse experts, and addressing both policies and values to enhance team cooperation towards common goals. The document also highlights challenges in collaboration and strategies to navigate them for effective outcomes.
More Related Content
Similar to Software design as a cooperative game with EventStorming
Software design as a cooperative game with EventStorming
- 1. Software design as aCooperative Game WitH @ziobrando
- 2. 9 Years Agoin Chile…
- 3.
- 4.
- 5.
- 6. Outcome (big Picture): Thewhole process is visible Massive learning (crossing silo boundaries) consensus around the core problem
- 7. Big Picture EventStorming Invitedthe right People! Explored the whole business end-to-end Visualized People and Systems Validated the storytelling Explored Value Discovered frictions and opportunities Identified the most compelling problem DELIVERED
- 8. Outcome (big Picture): Thewhole process is visible Massive learning (crossing silo boundaries) consensus around the core problem
- 9. The Official Ending “Let’smeet tomorrow to find a solution to this problem!” A validated business narrative A massive blocker
- 10. Our Homework Let’s usethe information gathered during the workshop to sketch possible Bounded Contexts
- 11.
- 12. Some Assumptions We’re workingon the most compelling problem The problem has a solution in Software and/or Process Key Experts are available Business people, from the departments involved Technical Experts: Software and Service/UX Designers
- 13. Scope: Epic orset of features Command Domain Event Domain Event Read Model Domain Event Read Model Preconditions OutcomesThe flow to discover
- 14. Hard Problems don’thave an Obvious solution
- 15.
- 16. A different job Bigpicture is for discovery -> Disagreements are OK Here we are Looking for an agreement -> Consensus is HARD
- 18. How to makeSpecialists with different BackGround cooperate towards a common goal?
- 19. Idea n°1: “TheEscape Room”
- 20. How to makeSpecialists with different BackGround cooperate towards a common goal? Without a Danger?
- 21.
- 22.
- 23. Game Rules: EventStormingDesign 1. Every Path Should be Completed 2. Colour Grammar Should be Respected 3. Every Stakeholder should be reasonably Happy 4. Every HotSpot should be addressed
- 24. Every Path ShouldBe Completed
- 26.
- 28.
- 29.
- 30. Colour-puzzle Thinking Policy User User Command Read Model ExternalSystem Domain Event Command
- 31. Do we ALWAYS needa Policy? Yes, My game, my rules
- 32. Investigate Policies How isour system supposed to react to given events? Whenever [Event] then [Command] “We need a lilac between the orange and the blue” Policy
- 33. This is whereeverybody lies
- 34. Ambiguity does notcompile
- 35. Policies spectrum IMPLICIT POLICIES:without an explicit agreement EXPLICIT POLICIES: assuming everyone is following them AUTOMATION: Listeners, Sagas, Process managers Policy User Policy
- 36. I am shapingthe conversation, more than the code.
- 37.
- 38. Expansion Set! For ExperiencedPlayers ;-)
- 39. Game Rules: EventStormingDesign 1. Every Path Should be Completed 2. Colour Grammar Should be Respected 3. Every Stakeholder should be reasonably Happy 4. Every HotSpot should be addressed 5. Aggregates should be coherent
- 41. Colour-puzzle thinking -again User Command Read Model External System Domain Event CommandPolicy Aggregate
- 42. Investigating Aggregates State MachineLogic Focus on BEHAVIOUR, not DATA Postpone NAMING Don’t fall in love with your intuition Aggregate
- 43. Symmetries on thetimeline Do something …possibly the something Policy Command Aggregate Domain Event Policy User External System Command Policy Command User Domain Event External System Domain Event Read Model Policy Command Aggregate Domain Event Policy Command Aggregate Domain Event Read Model Probably the same aggregate… Probably the same Policy…
- 44.
- 45. Pattern: Fuzzy byDesign Imprecise definitions… allow everyone to be included in the conversation. Allow Everything to be included in the model Trigger interesting conversation on the spot.
- 47. We need togive up something as individuals in order to succeed as a team
- 48.
- 49. Challenging value Every stepcan create or destroy value for given users Discovering multiple currencies Discovering new opportunities Discovering inconsistencies
- 50.
- 51. Dealing with Value Moneyis the Obvious one But it’s a Zero Sum Currency :-/ More interesting currencies follow: Time, Stress, Anxiety Joy, Reputation, Satisfaction …
- 52.
- 53.
- 54. Possibly your worstenemy
- 57.
- 58.
- 59. Rush To TheGoal Build a Baseline as quickly as possible Mark Every Alternative with a Hotspot Deliver Value to some Stakeholder Add your feedback with Hotspots
- 60. The Perfect Team Doesit even exist?
- 61. Competences Business From different Sides SoftwareDesign User Experience & Service Design …
- 62.
- 64. Need Diversity inorder to perform
- 65. Strategies & Complex Moves Thisis more up to you…
- 66.
- 67. Start from Thebeginning…
- 68. Start from theend: How can we get there?
- 71.
- 73. Openings Start from thebeginning More natural Easy to get Swamped Start from the end (Reverse Narrative) Lean, but less discoveries Not so natural for newbies Explore with Events -> Then Connect Needs Strict Timeboxing
- 74. I use allof them!
- 75.
- 77. Team Strategies Swarm: Everybodyon the problem Mob: One on the problem, everybody on feedback. Split & Merge
- 78.
- 79. Challenges Calendar Availability: wecan talk the same language, but not everybody at the same time. Organization Boundaries: External Software Supplier External UX design Agency Contract Boundaries & Professional Inertia: mandatory Deliverables
- 80.
- 81. What the businesssees Your Territory
- 82.
- 83. From vision todetail (and back) Big Picture Events Hot Spots, Systems, People Conflicts, Goals, Blockers, Boundaries Process Modelling Events + Policies, Commands, Read Models Value Proposition, Policies, Personas, Individual Goals Software Design Events + Aggregates Aggregates, Policies, Read Models, IDs
- 84.
- 85. We need togive up something as individuals in order to succeed as a team
- 86.
- 87. References • www.eventstorming.com • EventStormerson Google Groups • https://groups.google.com/forum/#!forum/eventstorming • LeanPub book in progress: • http://leanpub.com/introducing_eventstorming • Blog: • https://medium.com/@ziobrando • http://ziobrando.blogspot.com • Twitter: @ziobrando • Trainings & Workshop facilitation: info@avanscoperta.it • http://www.avanscoperta.it