<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[EventStorming - Medium]]></title>
        <description><![CDATA[EventStorming is a workshop format for quickly exploring complex business domains. - Medium]]></description>
        <link>https://medium.com/eventstorming?source=rss----b76a37724ddb---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>EventStorming - Medium</title>
            <link>https://medium.com/eventstorming?source=rss----b76a37724ddb---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 07:43:00 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/eventstorming" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Remote EventStorming]]></title>
            <link>https://medium.com/eventstorming/remote-eventstorming-8a00f303f11e?source=rss----b76a37724ddb---4</link>
            <guid isPermaLink="false">https://medium.com/p/8a00f303f11e</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ddd]]></category>
            <category><![CDATA[eventstorming]]></category>
            <category><![CDATA[event-sourcing]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Wed, 21 Jul 2021 07:32:41 GMT</pubDate>
            <atom:updated>2021-07-21T07:32:41.885Z</atom:updated>
            <content:encoded><![CDATA[<h4>EventStorming is not a single recipe for workshops. It comes in different flavors, and with different purposes.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cYvo8i1YzQj8W79N.png" /><figcaption>Here’s a little map of the relations between the Big Picture EventStorming recipe ingredients and what we can achieve during the workshop.</figcaption></figure><p>Before exploring the impact of turning it remotely, we need to make sure we understand what we’re talking about.</p><p>These are the most popular recipes for <a href="https://www.eventstorming.com/">EventStorming</a>.</p><ul><li><strong>Big Picture</strong> is used for project kick-offs, organization retrospectives and redesigns, startups envisioning and so on. It is mostly about <em>discovery</em>, and involves 20–30 people on average since multiple perspectives are needed.</li><li><strong>Process Modelling</strong> has a more focused scope, on a single cross-functional process, usually spanning multiple departments, and can involve 5–15 people depending on the process complexity.</li><li><strong>Software Design</strong> has more or less the same scope as Process Modelling but goes deeper into the internals of the software we’re designing.</li></ul><p>Read the <a href="https://blog.avanscoperta.it/2020/03/26/remote-eventstorming/">full story by Alberto Brandolini</a>!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a00f303f11e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eventstorming/remote-eventstorming-8a00f303f11e">Remote EventStorming</a> was originally published in <a href="https://medium.com/eventstorming">EventStorming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[EventStorming Workshop Facilitation for Software Development]]></title>
            <link>https://medium.com/eventstorming/eventstorming-workshop-facilitation-for-software-development-bbd6f923541?source=rss----b76a37724ddb---4</link>
            <guid isPermaLink="false">https://medium.com/p/bbd6f923541</guid>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[eventstorming]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Mon, 30 Mar 2020 10:42:57 GMT</pubDate>
            <atom:updated>2016-08-09T12:51:36.614Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_jz4itajC7tf8SzU_MwQpA.png" /><figcaption>by <a href="https://medium.com/u/73ee54d3cea">Alberto Brandolini</a></figcaption></figure><p>Developing complex software without a clear understanding of the underlying complexity is an invitation for troublesome implementation, scope creep and budget overruns.<br> <strong>EventStorming</strong> addresses these problems by allowing a <em>massive collective learning experience</em> around the business processes involved in an enterprise software development project.</p><p>In a <strong>single massively engaging workshop</strong> we will:</p><ul><li>build a<strong> Big Picture model of the business processes</strong> involved in a specific line of business, including <em>key software components</em>, <em>independent models</em>, <em>actors</em>, <em>external systems</em> and <em>key interactions</em>;</li><li>highlight the <strong>key impediments and blockers</strong> on the business flow;</li><li>explore and <strong>design solutions</strong> for the highest impact problems.</li></ul><p>That’s the <em>destination</em> but the journey could be even more interesting.</p><ul><li>Every participant will actively contribute, with questions, expertise, insights and doubts, all leading to a <strong>visible model</strong> of the collective level of understanding.</li><li>Participants will quickly <strong>learn a lot</strong> more about the nature of the larger system they’re working in.</li><li>Discussion will be triggered by the emergent model allowing <strong>deeper insights</strong> and <strong>solutions to long lasting problems</strong>.</li><li>A common understanding of large scale interaction will provide foundations for <strong>self-organisation</strong> around the emergent process.</li><li>A clear understanding of the <strong>whole complexity will allow people to make better choices</strong>, significantly reducing the project scope size.</li></ul><h4>How long will the workshop be?</h4><p>The <strong>standard format takes one day</strong>, divided in <em>two distinct parts</em>. The <strong>morning</strong> is dedicated to <strong>Big Picture exploration</strong>. It is usually highly interactive and <em>involves all the key roles</em> involved in the process. This is usually sufficient to <strong>highlight critical risks and blockers</strong> and select the n.1 problem to be solved.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*uVqSLsyEBlbhLnl7.png" /></figure><p>The <strong>afternoon</strong> will be a <strong>Design Level workshop</strong>, usually restricted to a <em>smaller number of people</em> directly involved in designing and implementing the solution to the highlighted problem. We’ll <strong>dig deeper into key interactions</strong>, understanding the motivations and the key enablers behind user decisions happening in the business flow. We’ll be guided into an emergent, loosely coupled, event-driven architecture that can provide critical breakthroughs in comparison with the current legacy implementation. <strong>Software designers</strong>, <strong>UX designers</strong> and<strong> business stakeholders</strong> will be cooperating towards a solution with the maximum business effectiveness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/560/0*AA1CzK190sR7vT-n.png" /></figure><h4>Who should we invite?</h4><p>The workshop is designed to provide a common ground for inter-discipline communication, and will adapt to the participants’ background, therefore we recommend to involve <strong>all the people involved in the actual problem solving</strong>. Ideally, a perfect match of <em>people with answers</em> and <em>people with questions</em>. This usually maps with the key stakeholders, the design and development team, plus a facilitator. Inclusion is far better than exclusion, so… whoever is interested in joining should be allowed to.</p><h4>How many people should participate?</h4><p>We facilitated workshop <strong>up to 30 people</strong> within a 1–2 days formula. More participants may require a special setting, and of course the location will have to be carefully selected. Afternoon session usually involves 5–10 participants.</p><h4>Can we participate remotely?</h4><p>No. The action will happen in one place. Remote participation won’t be nearly as effective as in- person.</p><h4>Why should we hire a facilitator?</h4><p>Having all the relevant people in the same room, without a plan to manage the interaction could be a recipe for disaster. <strong>A facilitator allows key people to focus on the learning and modelling experience only</strong>, taking the burden of managing the interaction. The facilitator <em>is not</em> involved in internal politics and could be free to speak out on critical issues.</p><h4>Are there special room requirements?</h4><p>Yes they are. Most of the activity will happen around the walls. Rooms with long straight walls (8–10 metres) work very well. Meeting rooms with a large table at the center should usually be avoided.</p><h4>Testimonials</h4><p><strong>EventStorming</strong> has been included in the last two edition of <strong>ThoughtWorks Technology Radar,</strong> as one of the <strong>most interesting emerging </strong><a href="https://www.thoughtworks.com/radar/techniques"><strong>techniques</strong></a>. It’s becoming a <em>de-facto</em> standard in the <strong>Domain-Driven Design community</strong>, for exploring and designing complex interactions. A wide range of organisations has benefited from it: from online marketplaces, to financial and trading institution; from small startups to large scale enterprises.</p><h4>Facilitator</h4><p><a href="https://medium.com/u/73ee54d3cea"><strong>Alberto Brandolini</strong></a><strong> is the inventor of EventStorming</strong> and author of <a href="https://leanpub.com/introducing_eventstorming"><em>Introducing EventStorming — An act of deliberate collective learning</em></a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/231/0*x5iMf2O_NEWaUXhL.jpeg" /></figure><p>His experience as <strong>software architect</strong>, <strong>agile coach</strong>, <strong>trainer</strong> and <strong>entrepreneur</strong> makes him the ideal translator for a wide variety of themes that will emerge during the workshop.</p><h4>Hire Alberto!</h4><p>Email: <a href="/service/mailto:info@avanscoperta.it">info@avanscoperta.it</a> <br>Follow Alberto on Twitter: <a href="https://twitter.com/ziobrando">@ziobrando</a></p><p><em>Originally published at </em><a href="http://www.avanscoperta.it/en/training/event-storming-workshop-2/"><em>www.avanscoperta.it</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbd6f923541" width="1" height="1" alt=""><hr><p><a href="https://medium.com/eventstorming/eventstorming-workshop-facilitation-for-software-development-bbd6f923541">EventStorming Workshop Facilitation for Software Development</a> was originally published in <a href="https://medium.com/eventstorming">EventStorming</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>