home.social

#eventstorming — Public Fediverse posts

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

  1. Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
    mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
    #SoftwareArchitektur im #Stream
    DIENSTAG 2026-07-28 13:00 CEST
    Mehr Informationen: software-architektur.tv/

  2. Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
    mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
    #SoftwareArchitektur im #Stream
    DIENSTAG 2026-07-28 13:00 CEST
    Mehr Informationen: software-architektur.tv/

  3. Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
    mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
    #SoftwareArchitektur im #Stream
    DIENSTAG 2026-07-28 13:00 CEST
    Mehr Informationen: software-architektur.tv/

  4. Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
    mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
    #SoftwareArchitektur im #Stream
    DIENSTAG 2026-07-28 13:00 CEST
    Mehr Informationen: software-architektur.tv/

  5. Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
    mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
    #SoftwareArchitektur im #Stream
    DIENSTAG 2026-07-28 13:00 CEST
    Mehr Informationen: software-architektur.tv/

  6. 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

  7. 🚀 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

  8. 🚀 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

  9. 🚀 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

  10. 🚀 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

  11. 🚀 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

  12. 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

  13. 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

  14. 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

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. 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

  25. 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

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

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

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

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

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

  31. 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

  32. 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

  33. 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

  34. 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

  35. 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

  36. 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

  37. 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

  38. 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-

  39. 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-

  40. I've been facilitating the 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 : architecture-weekly.com/p/the-

  41. 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-

  42. 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-

  43. 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. 👇

  44. 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. 👇

  45. 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. 👇