#eventstorming — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #eventstorming, aggregated by home.social.
-
Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
Aufnahme verfügbar!
https://software-architektur.tv/2026/07/28/folge326.html -
Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
Aufnahme verfügbar!
https://software-architektur.tv/2026/07/28/folge326.html -
Kollaborative Modellierung - warum und wie funktioniert Event Storming in der Praxis
-
Unser neues #EventStorming kollaborative Modellierung Training!
Mit Tom Asel @Tom_Asel , Daniel Sack und mir bei @socreatory -
Unser neues #EventStorming kollaborative Modellierung Training!
Mit Tom Asel @Tom_Asel , Daniel Sack und mir bei @socreatory -
Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
#SoftwareArchitektur im #Stream
HEUTE 13:00 CEST
Mehr Informationen: https://software-architektur.tv/ -
Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
#SoftwareArchitektur im #Stream
HEUTE 13:00 CEST
Mehr Informationen: https://software-architektur.tv/ -
Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
#SoftwareArchitektur im #Stream
MORGEN 13:00 CEST
Mehr Informationen: https://software-architektur.tv/ -
Kollaborative Modellierung - warum und wie funktioniert #EventStorming in der Praxis
mit Tom Asel @Tom_Asel , Daniel Sack und Eberhard Wolff
#SoftwareArchitektur im #Stream
MORGEN 13:00 CEST
Mehr Informationen: https://software-architektur.tv/ -
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: https://software-architektur.tv/ -
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: https://software-architektur.tv/ -
The response to the #IDDD Tour has been tremendous! To accommodate the waitlist, #VaughnVernon has added a second date: June 15–18.
Register here: https://kalele.io/training/iddd/
$400 seats — $1,600 OFF -
🚀 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):
https://kalele.io/training/iddd/
🎟️ $400 seats — $1,600 OFF.
-
🚀 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):
https://kalele.io/training/iddd/
🎟️ $400 seats — $1,600 OFF.
-
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
-
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
-
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: https://www.avanscoperta.it/en/training/collaborative-software-design-workshop/
#CollaborativeModelling #DomainDrivenDesign #EventStorming -
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: https://www.avanscoperta.it/en/training/collaborative-software-design-workshop/
#CollaborativeModelling #DomainDrivenDesign #EventStorming -
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:
https://discord.com/events/1154124413126582272/1463361406614372393
-
How do facilitators include color blind folks in an event storming workshop? #EventStorming #DomainDrivenDesign
-
How do facilitators include color blind folks in an event storming workshop? #EventStorming #DomainDrivenDesign
-
Wrote some thoughts and an idea on event-mapping applications and would love some feedback on https://rimann.org/blog/20250720-event-mapping-tool/
#opensource #architecture #development #diagram #eventstorming #eventmapping #eventsourcing
-
Wrote some thoughts and an idea on event-mapping applications and would love some feedback on https://rimann.org/blog/20250720-event-mapping-tool/
#opensource #architecture #development #diagram #eventstorming #eventmapping #eventsourcing
-
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?
-
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.
https://www.qwan.eu/2025/06/02/ddd-case.html
#dddeu -
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.
https://www.qwan.eu/2025/06/02/ddd-case.html
#dddeu -
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: https://www.architecture-weekly.com/p/the-underestimated-power-of-hot-spots
-
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: https://www.architecture-weekly.com/p/the-underestimated-power-of-hot-spots
-
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. 👇
-
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. 👇
-
«CoMo soll das Fachwissen aus den Köpfen der Fachleute in die Köpfe von Entwicklerinnen, Testerinnen, Product Ownern, Produktmanagern und Business-Analysten transportieren»
Collaborative Modeling: Software-Architektur mit den Stakeholdern gestalten | Developer https://www.heise.de/hintergrund/Collaborative-Modeling-Software-Architektur-mit-den-Stakeholdern-gestalten-10371860.html
#CollaborativeModeling #StakeholderEngagement #DomainDrivenDesign #RequirementsEngineering #CoMo #EventStorming #DomainStorytelling #ExampleMapping #UserStoryMapping #Teamwork #ProjectManagement #Projektmanagement -
«CoMo soll das Fachwissen aus den Köpfen der Fachleute in die Köpfe von Entwicklerinnen, Testerinnen, Product Ownern, Produktmanagern und Business-Analysten transportieren»
Collaborative Modeling: Software-Architektur mit den Stakeholdern gestalten | Developer https://www.heise.de/hintergrund/Collaborative-Modeling-Software-Architektur-mit-den-Stakeholdern-gestalten-10371860.html
#CollaborativeModeling #StakeholderEngagement #DomainDrivenDesign #RequirementsEngineering #CoMo #EventStorming #DomainStorytelling #ExampleMapping #UserStoryMapping #Teamwork #ProjectManagement #Projektmanagement -
@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 :-) ) . -
@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 :-) ) . -
@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 -
Events, Event Sourcing und CQRS