home.social

#eventstorming — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #eventstorming, aggregated by home.social.

  1. The response to the #IDDD Tour has been tremendous! To accommodate the waitlist, #VaughnVernon has added a second date: June 15–18.

    Register here: kalele.io/training/iddd/
    $400 seats — $1,600 OFF

    #VaughnVernon #DDD #DomainDrivenDesign #EventStorming

  2. 🚀 The #IDDD Tour is back!

    #VaughnVernon is bringing the spirit of the legendary 2013 world tour to a hands-on online “Implementing Domain-Driven Design” workshop (June 8–11):

    kalele.io/training/iddd/

    🎟️ $400 seats — $1,600 OFF.

    #DDD #DomainDrivenDesign #EventStorming

  3. 🚀 The #IDDD Tour is back!

    #VaughnVernon is bringing the spirit of the legendary 2013 world tour to a hands-on online “Implementing Domain-Driven Design” workshop (June 8–11):

    kalele.io/training/iddd/

    🎟️ $400 seats — $1,600 OFF.

    #DDD #DomainDrivenDesign #EventStorming

  4. 🚀 The #IDDD Tour is back!

    #VaughnVernon is bringing the spirit of the legendary 2013 world tour to a hands-on online “Implementing Domain-Driven Design” workshop (June 8–11):

    kalele.io/training/iddd/

    🎟️ $400 seats — $1,600 OFF.

    #DDD #DomainDrivenDesign #EventStorming

  5. 🚀 The #IDDD Tour is back!

    #VaughnVernon is bringing the spirit of the legendary 2013 world tour to a hands-on online “Implementing Domain-Driven Design” workshop (June 8–11):

    kalele.io/training/iddd/

    🎟️ $400 seats — $1,600 OFF.

    #DDD #DomainDrivenDesign #EventStorming

  6. 🚀 The #IDDD Tour is back!

    #VaughnVernon is bringing the spirit of the legendary 2013 world tour to a hands-on online “Implementing Domain-Driven Design” workshop (June 8–11):

    kalele.io/training/iddd/

    🎟️ $400 seats — $1,600 OFF.

    #DDD #DomainDrivenDesign #EventStorming

  7. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  8. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  9. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  10. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  11. Some of those stickies at the bottom of the board are still open questions. Good. Better to ask them here than have someone answer them quietly in a pull request.
    Architecture is already happening across the whole room. The question is whether we make it visible.

    This is part of day two of my DDD foundation workshop, and honestly one of my favourite conversations to facilitate.

    #DomainDrivenDesign #CollaborativeModelling #EventStorming #SoftwareArchitecture #TeamTopologies

  12. You'll leave able to facilitate your first collaborative modelling session with your team. Not just knowing the theory, but having practiced the facilitation skills needed to actually do it.
    We don't run public workshops often—most of our training is in-house with companies. If you've been wanting to start with collaborative modelling but unsure how, this is your chance to learn by doing it.

    Details: avanscoperta.it/en/training/co
    #CollaborativeModelling #DomainDrivenDesign #EventStorming

  13. Tonight (8 PM Berlin time,) there is a little online Meet-UP of the #ddd #DomainDrivenDesign Group, where we will "practice" #EventStorming

    The group is on Discord and it looks like a nice place to hang out.. and exchange ideas:

    discord.com/events/11541244131

  14. How do facilitators include color blind folks in an event storming workshop? #EventStorming #DomainDrivenDesign

  15. Jeśli nie znacie #EventStorming, to - nawet, jeśli nie zamierzacie go używać - warto poznać koncepcję. A któż może ją lepiej wytłumaczyć niż jej twórca, czyli Alberto Brandolini podczas prezentacji na konferencji?

    #DDD #Domain

    youtube.com/watch?v=mLXQIYEwK24

  16. This week, we open sourced our #EventStorming case. Celebrating #DDDEurope, which I’m currently visiting. We have learnt a lot from the community and want to give something back.
    qwan.eu/2025/06/02/ddd-case.ht
    #dddeu

  17. This week, we open sourced our case. Celebrating , which I’m currently visiting. We have learnt a lot from the community and want to give something back.
    qwan.eu/2025/06/02/ddd-case.ht

  18. This week, we open sourced our #EventStorming case. Celebrating #DDDEurope, which I’m currently visiting. We have learnt a lot from the community and want to give something back.
    qwan.eu/2025/06/02/ddd-case.ht
    #dddeu

  19. This week, we open sourced our #EventStorming case. Celebrating #DDDEurope, which I’m currently visiting. We have learnt a lot from the community and want to give something back.
    qwan.eu/2025/06/02/ddd-case.ht
    #dddeu

  20. This week, we open sourced our #EventStorming case. Celebrating #DDDEurope, which I’m currently visiting. We have learnt a lot from the community and want to give something back.
    qwan.eu/2025/06/02/ddd-case.ht
    #dddeu

  21. I've been facilitating the #EventStorming sessions for years now, and something keeps catching my attention.

    While teams naturally focus on mapping out those orange event sticky notes (the backbone of any EventStorming session), they often underestimate the power of two critical elements: Hot Spots and Notes.

    What I value most about Hot Spots and Notes isn't just how they improve workshops - it's how they change team culture around uncertainty.

    In technical discussions, we often feel pressure to know everything immediately.

    Hot Spots create permission to say, "I don't know yet" while still making progress. They transform uncertainties from conversation-killers into clearly defined next steps.

    I've seen teams evolve from hiding what they don't know to actively hunting for uncertainties as valuable information. Questions become assets rather than liabilities.

    If you're incorporating EventStorming into your toolkit, don't underestimate these powerful elements. They might not get as much attention as domain events, but in my experience, they often separate a productive modelling session from a frustrating stalemate.

    Read more in the latest #ArchitectureWeekly: architecture-weekly.com/p/the-

  22. In #EventStorming Workshops kommen schnell viele Domain Events zusammen – und genau das macht es oft schwer, den Blick fürs Wesentliche zu behalten.


    Michael Plöd zeigt in seinem Blogpost, wie sich mithilfe 9 einfacher Heuristiken Pivotal Events erkennen lassen: Ereignisse, die zum Beispiel nachgelagerte Aktivitäten auslösen, Zustände verändern oder wichtige Geschäftsentscheidungen markieren.

    🔗 Link zum Blogpost in den Kommentaren. 👇

  23. @marick not me, but thanks to your wikipedia link and @k9ox 's link to #elixir / #erlang behaviours, maybe several things are is starting to fall into place.
    FYI I remember @marcevers being keen on DCI, but it didn't speak to me at the time. I now see links with the kind of designs that flow from #EventStorming . And somehow behaviours in #elixir make sense. I was programming a distributed system in #PhoenixLiveView without noticing (until the book pointed it out, that is :-) ) .

  24. @marick not me, but thanks to your wikipedia link and @k9ox 's link to #elixir / #erlang behaviours, maybe several things are is starting to fall into place.
    FYI I remember @marcevers being keen on DCI, but it didn't speak to me at the time. I now see links with the kind of designs that flow from #EventStorming . And somehow behaviours in #elixir make sense. I was programming a distributed system in #PhoenixLiveView without noticing (until the book pointed it out, that is :-) ) .

  25. @marick not me, but thanks to your wikipedia link and @k9ox 's link to #elixir / #erlang behaviours, maybe several things are is starting to fall into place.
    FYI I remember @marcevers being keen on DCI, but it didn't speak to me at the time. I now see links with the kind of designs that flow from #EventStorming . And somehow behaviours in #elixir make sense. I was programming a distributed system in #PhoenixLiveView without noticing (until the book pointed it out, that is :-) ) .

  26. @marick not me, but thanks to your wikipedia link and @k9ox 's link to #elixir / #erlang behaviours, maybe several things are is starting to fall into place.
    FYI I remember @marcevers being keen on DCI, but it didn't speak to me at the time. I now see links with the kind of designs that flow from #EventStorming . And somehow behaviours in #elixir make sense. I was programming a distributed system in #PhoenixLiveView without noticing (until the book pointed it out, that is :-) ) .

  27. @marick not me, but thanks to your wikipedia link and @k9ox 's link to #elixir / #erlang behaviours, maybe several things are is starting to fall into place.
    FYI I remember @marcevers being keen on DCI, but it didn't speak to me at the time. I now see links with the kind of designs that flow from #EventStorming . And somehow behaviours in #elixir make sense. I was programming a distributed system in #PhoenixLiveView without noticing (until the book pointed it out, that is :-) ) .

  28. On the way home from a great #EventStorming workshop with Alberto Brandolini (@ziobrando). Learning the method, getting valuable tips about the technique, meeting amazing people is one thing... But when a workshop is this engaging, one's motivation for using the learnings in practice skyrockets.
    #ddd

  29. 2 Meet-Up tips for this week.
    The first one is tonight in Berlin. The inventor of #EventStorming is in the house:
    Collaborative Modeling Meetup with special guest Alberto Brandolini! Again!

    meetup.com/domain-driven-desig

    And the 2nd one is online on Thursday. A meet-up where we talk about all things #agile / #scrum was organized by Tobias Mayer. Usually, we go very deep and philosophical here. Great likeminded souls:
    meetup.com/de-DE/agile-convers

  30. My sketch note of Alberto Brandolini's talk "Modelling up!"

    buff.ly/436zUmh

    The talk was a bit chaotic (at least for me), which is never good for a sketch note 😅

    #SketchNote #EventStorming

  31. @kenny_baas @ahl @diana @selketjah
    so true! Everyone who tried collaborative modeling should know better. But still, in so many companies I worked all these things where done by a single person, working with „requirements“. Which books are you referring to? I might them to my article about #eventstorming

  32. With a couple of friends from the community, I’m organizing the ComoCamp—an unconference that brings together the makers and masters of collaborative modeling methods like #EventStorming, #UserStoryMapping, and #DomainStorytelling

    comocamp.org

    #comocamp #collaborativemodeling #dddesign

  33. With a couple of friends from the community, I’m organizing the ComoCamp—an unconference that brings together the makers and masters of collaborative modeling methods like #EventStorming, #UserStoryMapping, and #DomainStorytelling

    comocamp.org

    #comocamp #collaborativemodeling #dddesign

  34. With a couple of friends from the community, I’m organizing the ComoCamp—an unconference that brings together the makers and masters of collaborative modeling methods like #EventStorming, #UserStoryMapping, and #DomainStorytelling

    comocamp.org

    #comocamp #collaborativemodeling #dddesign

  35. With a couple of friends from the community, I’m organizing the ComoCamp—an unconference that brings together the makers and masters of collaborative modeling methods like #EventStorming, #UserStoryMapping, and #DomainStorytelling

    comocamp.org

    #comocamp #collaborativemodeling #dddesign

  36. With a couple of friends from the community, I’m organizing the ComoCamp—an unconference that brings together the makers and masters of collaborative modeling methods like #EventStorming, #UserStoryMapping, and #DomainStorytelling

    comocamp.org

    #comocamp #collaborativemodeling #dddesign

  37. We were all around a wall, doing #EventStorming, when it became visible between the current and desired flow. The team quickly assessed what they could do by visualizing and discussing options. It moved on to implement a model that not only addressed new business requirements but also allowed them to tidy the current landscape.

    Remember, thinking in systems! 🚀

    By thinking in systems, have you ever had a similar experience? 💡

    #systemsthinking #opensystems #softwarearchitecture

    5/5