<?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[Stories by Avanscoperta on Medium]]></title>
        <description><![CDATA[Stories by Avanscoperta on Medium]]></description>
        <link>https://medium.com/@avanscoperta?source=rss-a22cb412fcb3------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ayp19qAEbbdiBOZbAJFf-w.png</url>
            <title>Stories by Avanscoperta on Medium</title>
            <link>https://medium.com/@avanscoperta?source=rss-a22cb412fcb3------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:10:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@avanscoperta/feed" 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-a22cb412fcb3------2</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[The Marathon of the Management]]></title>
            <link>https://medium.com/avanscoperta-we-are-learners/the-marathon-of-the-management-e621a0a2b53c?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/e621a0a2b53c</guid>
            <category><![CDATA[scaling]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[portfolio-management]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Fri, 23 Oct 2020 08:26:40 GMT</pubDate>
            <atom:updated>2020-10-23T08:35:35.088Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g2bZwjkPJASDfL-TOOAThA.png" /></figure><h4>Jacopo Romei interviews Gaetano Mazzanti</h4><p><em>Looking for the Italian version of the interview? Find it here: </em><a href="https://blog.avanscoperta.it/it/2020/04/08/presente-e-futuro-del-management-la-metafora-della-maratona/?utm_source=blog&amp;utm_medium=post&amp;utm_campaign=portfolio_management"><em>Presente e futuro del Management: la metafora della maratona</em></a><em>.</em></p><p>What happens when you arrange a chat between Jacopo Romei (Strategic consultant) and Gaetano Mazzanti (Agile Coach at agile42)?<br>An unexpected mix of music, marathons, risk, change, fragility, lean thinking, portfolio management, company culture…<br>Two of the greatest minds within the Italian and international Agile landscape get together for this exchange, with some true gems and surprising stories, as well as a realistic and to-the-point analysis on the state of the art of the Managerial culture.</p><p>Enjoy!</p><p><strong>Jacopo</strong>: Hello, Gaetano! It’s a pleasure being able to do this interview with you. We’ve known each other for ages, but we never had a chance for a real one-to-one. I feel like I’ve known you since forever. Actually… where did we meet? Do you remember?</p><p><strong>Gaetano</strong>: Hey, Jacopo. That’s true, ages! :) I don’t remember where we first met either. I think it’s a good sign.</p><p><strong>Jacopo</strong>: Yes, that must be a good sign indeed. I must say in all these years I’ve learned so much about you. Other than your work as an Agile Coach — which we’ll talk about soon — I know you’re a great pianist and a passionate long-distance runner!</p><p><strong>Gaetano</strong>: I learned piano when I was a kid, and, when I reached the 8th (out of 10) year of Conservatory, I had to choose: music or Astronomy, and I went for University. I never looked back, but I’ve always been playing. I play (almost) every genre: jazz, fusion, rock, and I even get the chance to jump on stage with my old bands. And, by the way, I’m not a great pianist! (smiles, ed.).</p><p><strong>Jacopo</strong>: And have you always been passionate about running?</p><p><strong>Gaetano</strong>: I started running back in 2012. It began as a challenge with my partner: let’s see if we could run a half-marathon within two months. We won the challenge, and then I run 18 marathons since, including the 6 World Majors.</p><p><strong>Jacopo</strong>: Unbelievable. And what’s the meaning of these two activities for you?</p><p><strong>Gaetano</strong>: In a musical band, you learn how to collaborate, to leave space to others, and to understand when it’s your moment. By playing in a band, you learn a lot of things about how the world goes. Nothing like music, jazz in particular, allows mixing the logical and rational part of me with the crazy and creative one.</p><p>I’ll tell you something very few people know: it was my passion for music, especially electronic music, that, together with my fixation with computers, became my first source of income when I was a teenager. I’ve written the programs for the synths produced by Yamaha Music Italia, which were coded on Mac and Amiga. Good old times!</p><p><strong>Jacopo</strong>: Wow! I can see some pretty nerd roots coming out here. And what type of satisfaction does running give you?</p><p><strong>Gaetano</strong>: Running means many things. There’s a challenge with yourself. The push to never stop improving your performance or, as years go by, to fight the effects of aging. Then you have the training sessions, which are very tough if you want to run a marathon, mentally more than physically. Your head keeps saying “stop it, that’s it”, and your determination only will allow you to continue. You also consider the joy of hitting your target or the will to give it another try if you failed. These are very intense feelings. I won’t stop (unless I hurt myself).</p><p><strong>Jacopo</strong>: Your head keeps saying “stop it, that’s it”. Abruptly, this makes me think about some of my old “corporate” clients. Have you ever felt the same when working with some very dysfunctional company?</p><p><strong>Gaetano</strong>: Absolutely! :) When you start a change process (or transformation or anything you wanna call it), this is like a marathon both for the coach and for those the coach is working with. This similarity offers some interesting insights: it’s not like you buy a book about running, and the next day you run 42 km. You must run 10 km, then a half marathon, and so on. You will get there one step at a time, make mistakes, walk your own path, fail, and learn. There are no shortcuts. It’s not like a degree or a driving license, something you can buy if you want (leaving any moral judgment aside).</p><p><strong>Jacopo</strong>: Did you mean “certification”? :-D</p><p><strong>Gaetano</strong>: It’s very fashionable nowadays to “buy” a scaling framework. You just follow the recipe and there you go, your company will become agile. That’s not how it works. It simply cannot work that way.</p><p><strong>Jacopo</strong>: Please carry on, I like what I’m hearing.</p><p><strong>Gaetano</strong>: A very common scenario is “let’s arm ourselves and you go to war”: the management just want to “transform their teams and make them agile”, “accelerate the teams”, whilst them, the actual managers, well they keep acting in the same old way as if nothing has changed, except perhaps attending some useless events and rituals prescribed by the framework they adopted. Sometimes they do it in good faith, they literally can’t get out of their mental habits. Of course, this approach is bound to fail too.</p><p>In fact, lately, our job has involved more and more helping people from the medium-upper levels of the organizations.</p><p><strong>Jacopo</strong>: Same here, I can relate.</p><p><strong>Gaetano</strong>: If you don’t help them, and if you don’t work with them constantly, they simply can’t make it.</p><p>Having said that, even when running a marathon, sometimes, it’s better to stop than to get hurt!</p><p><strong>Jacopo</strong>: This metaphor makes sense!</p><p><strong>Gaetano</strong>: Looking for a ready-to-go solution and assuming this solution will also work in your specific case is quite dangerous, just because that very solution was born in another context. Maybe it was designed and prepared beforehand and on purpose!</p><p><strong>Jacopo</strong>: “Take these pills, they worked for me!”</p><p><strong>Gaetano</strong>: The boss of a company I used to work for — a listed company — used to say this sentence every time there was something new to learn and master: but can’t we just buy it? He even used to ask it for things such as… learning English. (We both laugh, ed.).</p><p><strong>Jacopo</strong>: It’s happening again: a lot of people now want to become agil… ehm, sorry, EFFECTIVE by buying a badge, a piece of paper. True. Considering what we just said, how do you evaluate the future of management in the software world? And not only in software, of course.</p><p><strong>Gaetano</strong>: I’m not too optimistic about this. It’s been a while since this whole thing emerged.</p><p>On one hand, you have big management schools, with their big fees to get an MBA, and on the other hand, you have a more bottom-up approach. They both operate in very “toxic” contexts and they both keep teaching the same things over and over, the same ideas, the same ways to do things. We’re losing the battle. We need a huge crisis… will COVID help us? (This interview was conducted in the first half of 2020, ed.)</p><p><strong>Jacopo</strong>: Who knows? We shall see!</p><p><strong>Gaetano</strong>: I see a huge resistance at all levels. Only small companies are doing different things, not only in Italy. There’s so much bullshit about types of leadership, even agile leadership, and so many workshops on sale… and then they go back to their office and they start going: “yes, I’d like to do it, but I cannot commit to that, not here… ” I don’t know. These are very dark times.</p><p><strong>Jacopo</strong>: Come on, it’s not that bad! There’s the whole Avanscoperta community ready to throw new light on this scenario. LEGIONS of revolutionaries armed to the teeth! Ahah!</p><p>Let’s talk about the workshop you’re doing with Avanscoperta, titled<a href="https://www.avanscoperta.it/en/training/modern-portfolio-management/?utm_source=blog&amp;utm_medium=post&amp;utm_campaign=gaetano_mazzanti"> Modern Portfolio Management</a>.</p><p>In the workshop description, you say “the equation Agile Team = Business Agility is wrong. I agree with you that’s the reason why I’ve been dealing with contracts for the past 10 years. What’s the reason behind the above quote?</p><p><strong>Gaetano</strong>: Let’s go back to the disconnection between management and those looking after a project. You can do cool stuff with the teams, but then all the decision-making processes, how to allocate teams, why, and with which criteria, all these elements make the whole thing useless. and the worst thing is, this never happens for business reasons, rather for political reasons, internal fights, bonuses…</p><p>Those who actually do the job, poor them, eventually they’re stuck between contrasts, dependencies, sudden stops to the projects, “let’s start again” and so they’re just destroyed by the whole situation. All the feedback mechanisms (which could keep the projects steady at least) are compromised. Portfolio Management can be a good solution to many of these problems.</p><p><strong>Jacopo</strong>: What’s the added value of your workshop if this is seen from the perspective of the management, generally speaking?</p><p><strong>Gaetano</strong>: Awareness to start with. This whole thing is about money! Embracing the Portfolio Management approaches means making more money, full stop. Making choices that bring more financial efficiency in the long term. Starting a new initiative costs money and you’ll get that money back only if and when you close up that initiative. We’re very good at starting new things but often these initiatives stop or slow down significantly and every time this happens we lose money: all the conversations, the estimates (!), the planning, the uncompleted work it’s all money that is lost.</p><p><strong>Jacopo</strong>: Hey, are you talking in lean thinking terms?</p><p><strong>Gaetano</strong>: Here’s what lean is all about: make things lighter and understand how to direct our choices to take different paths, such as the triage lanes, to manage our initiatives more smartly, by focusing on the ones with higher return hedging the risks we take. Past mechanisms create a lot of overwork: we start a lot of things and we close very few of them.</p><p><strong>Jacopo</strong>: Uh, wasn’t it true that backlogs can host an infinite number of user stories? (I smile sardonically, e.d.).</p><p><strong>Gaetano</strong>: Sometimes it’s also a product architecture problem, but we often spend a lot of time, too much, to deal with dependencies, and this shouldn’t happen. The same goes for estimates: is it always worth to make estimates? Often, no. Let’s take an example: you estimate “with precision” how long it takes you to develop something but then when considering the whole end to end flow the development lead time is irrelevant!</p><p><strong>Jacopo</strong>: Ah! That’s my nightmare. My number 1 enemy, my nemesis. I used to work for a company where developers were often blamed for being too slow. Then you went to check out the kanban board and you could see a huge quantity of developed items “in the queue” which were not released because they were not needed… Do you think this is just an Italian problem or do you see it happening abroad too?</p><p><strong>Gaetano</strong>: No, I’ve seen it abroad too and even with clients whose quotes, pictures and presentations we usually bring with us as examples. We believe Italians are the best when it comes to “how can you say no to a request?”. The idea that saying “no” can be smarter financially is considered blasphemy. I’ve dealt with some managers who reacted even violently to this. Once I had a call with a CEO and it ended up with him telling me “no, you can’t do this, you can’t say these things”.</p><p><strong>Jacopo</strong>: I can relate to this, insults included! And why would join your workshop be a solution to this very problem?</p><p><strong>Gaetano</strong>: Maybe not a “solution”, but it can surely provide some “hooks” and techniques that can enable some healthy discussions and a convincing way of thinking. What shall we kick off straight away? How to balance the workload? If there are any highly-specialized workers, how do we decide where, how, and when to allocate them? There will practical and operational parts, and even some new bits such as the triage table, useful to make the lead time/shelf life relationship explicit, and the payoff on other things too. We’re gonna explain these activities during the workshop: they’re very easy to understand at all levels and extremely effective. We’re also gonna talk about a useful approach to manage dependencies (or to avoid doing that!) which can indeed be very useful.</p><p><strong>Jacopo</strong>: I literally can’t wait.</p><p><strong>Gaetano</strong>: We’re also gonna cover when to kick off a project with various degrees of risk. This will be done taking into account other things besides the release date, based on forecasting the impact of this activity on the overall economy of the company, and we’ll assess when it’s useful to make estimates and when it’s not, all of this also taking advantage of the Cynefin Framework.</p><p><strong>Jacopo</strong>: A must-attend workshop. I can’t wait. Thanks, Gaetano! Do you have a final message for our readers?</p><p><strong>Gaetano</strong>: The only thing that matters is understanding what kind of decisions you have to make, how, with whom and when. “I wish it was that easy”, I hear you! (He laughs, e.d.). And then keeping the focus on finishing things and not on starting them, we can’t afford to throw money away. I think that’s enough from me!</p><h4>Learn with Gaetano Mazzanti</h4><p>Gaetano is the author of the <a href="https://www.avanscoperta.it/en/training/modern-portfolio-management/?utm_source=blog&amp;utm_medium=post&amp;utm_campaign=gaetano_mazzanti">Modern Portfolio Management Workshop</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e621a0a2b53c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avanscoperta-we-are-learners/the-marathon-of-the-management-e621a0a2b53c">The Marathon of the Management</a> was originally published in <a href="https://medium.com/avanscoperta-we-are-learners">Avanscoperta - We Are Learners</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[From ziobrando to EventStorming]]></title>
            <link>https://medium.com/avanscoperta-we-are-learners/from-ziobrando-to-eventstorming-97e5d17b5a59?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/97e5d17b5a59</guid>
            <category><![CDATA[eventstorming]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ddd]]></category>
            <category><![CDATA[orange]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Wed, 11 Oct 2017 14:48:44 GMT</pubDate>
            <atom:updated>2017-10-12T08:18:16.816Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yRL7l9V8IdEi3X_jtNVGwg.png" /><figcaption>Alberto Brandolini in action at DDD Europe 2016 showing one of his world-famous slides</figcaption></figure><h4>Q&amp;A with Alberto Brandolini</h4><p>Avanscoperta’s founder <strong>Alberto Brandolini</strong> is the inventor of <strong>EventStorming</strong>, the author of the book “Introducing EventStorming”, and much more…</p><p>Enjoy!</p><p><em>Avanscoperta</em>: <a href="http://www.avanscoperta.it/en/trainer/a-brandolini/">Alberto Brandolini</a> is a coach, a trainer, a businessman, a speaker, an author, but most importantly, he’s <strong>ziobrando</strong>. We’re very curious now… who was the first one to call you ziobrando?</p><p><em>Alberto Brandolini</em>: Lamberto, the guy who used to sit next to me in secondary school. Then, when I was in high school, comics were very popular, and Marty Mystere (the Good Old Marty) just helped reinforce the whole thing. The nickname kind of got out of use during the university years. When it came to create my digital identity online, meaning the first username, a blog… <strong>ziobrando was the name of choice</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/474/1*XQf_z2deJ9bMMznVQUaORA.png" /><figcaption>@ziobrando’s drawings and hand-writing play a key role in his talks and workshops</figcaption></figure><p>It wasn’t the most clever choice at first because all blogs used to list their sources and names in alphabetical order, so I always ended up at the bottom of the list.</p><p>Oh yes, and then there was the time everyone was like “you named yourself Zio Brando so that you can be the Italian version of Uncle Bob” (“zio” meaning both “uncle” and “buddy” in Italian), but you must know that back in 1982, when the nickname was invented, I had no clue about who Uncle Bob was! Since Twitter, all things fell into place nicely again.</p><p><em>Avanscoperta</em>: It was 2006, the year you signed the <a href="http://agilemanifesto.org/iso/it/manifesto.html">Agile Manifesto</a>. Can you tell us the before and after of this signature?</p><p><em>Alberto Brandolini</em>: Well, actually it took me a while to understand I could sign the Manifesto and that it was something of my concern, but then is was 2001 when I started my first enterprise project with Kent Beck’s <a href="https://www.amazon.co.uk/Extreme-Programming-Explained-Embrace-Change/dp/0321278658">“eXtreme Programming Explained”</a> on my desk. It was a project in the banking field and it was then when we started experimenting some techniques: the first <strong>JUnit</strong> tests (they were embarassing, believe me!), Continuous Integration, and so on.</p><p>They worked. Results were coming in. So we didn’t stop.</p><p>I got “hit” the second time when I discovered Alistair Cockburn’s <a href="https://www.amazon.com/Agile-Software-Development-Cooperative-Edition/dp/0321482751">“Agile Software development: the Cooperative Game”</a>, where topics such as communication and information radiators were explained, and there I started understanding that I could (and I had to) question all old procedures and habits.</p><p>A couple of books and projects later, the signature of the Manifesto became a mere formality, just like being married after you’ve lived together with your partner for a few years.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/592/1*ZAzlAKXyGzYva1hfwSYiyA.png" /><figcaption>As the old saying goes, “It’s never too late!”</figcaption></figure><p>After the signature, things did not change much. But <strong>gradually Agile was becoming more important in all the things I was doing</strong>: I found out I was not “the only one who read the book in Italy” and that I could rely on a community that I did not know at first. I approached this community prudently, but then I realized how awesome this was, something I still think.</p><p>And the same happened at the European level.</p><p>You see, <strong>maybe the difference from the beginning is that now I feel part of this community</strong>. Let me put this right: I am <strong>fucking</strong> proud of being part of it.</p><p><em>Avanscoperta</em>: What is status of the world of software development in 2016, and where would we like it to be?</p><p><em>Alberto Brandolini</em>: There’s no such a thing as a “place to be”. It’d be good if there was a line, with something like a Nirvana towards the bottom and a spot saying “we’re at 75%”.</p><p>Too easy. <strong>The world of software development is a shapeless mass</strong> where you can find professionals who model space and time around themselves in order to produce something amazing, and companies whose practices border slavery and that treat their developers like numbers or replaceable resources. These companies deliver terrible, faulty services and products which make their users’ life a nightmare.</p><p>One is led to believe that all these differences and the extension of the range of things included in this shapeless mass has not been fully understood yet. <strong>The rules of the game are not the same for everyone</strong>: you cannot behave like you’re doing agile in a company where turnover never stops. Or where software development is subject to financial constrictions that don’t take into account the peculiarity of the ecosystem.</p><p>What I’m witnessing is a community where people start understanding that <strong>the rules of the game are different</strong>, that developing software is something “the management” has not fully understood yet, and that this cannot be successful if you ignore the peculiarity of your ecosystem. And this community is growing, and it’s obtaining results. But there’s still so many people who are not at the forefront yet, and they keep on living the contradiction between what is working well on a small, local scale, and the old, traditional management rules which they’re not able to question yet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*Cqp8sNu9bMbH5RxVHH30vA.jpeg" /><figcaption>Dave Grohl’s always been a great inspiration for Alberto… did you know @ziobrando plays drums?</figcaption></figure><p>Where would we like to be? <strong>Sometimes one believes this fight is a David-Goliath one</strong>. For each professional who starts doing things in the right way, there’s an endless number of graduates who are approaching the job market whose heads are full of bad ideas. We had the luxury to wait for this situation to change when this type of paradigm shift used to happen in the past.</p><p>Quoting Planck: “A new scientific truth does not triumph by convincing its opponents and making them see the light, but rather because its opponents eventually die, and a new generation grows up that is familiar with it.” <strong>In our field the paradigms shift faster than the generations</strong>, but “convincing” hasn’t become easier yet.</p><p><em>Avanscoperta</em>: Understanding the system with <a href="http://eventstorming.com/">EventStorming</a>. Where do we start, how does it work and why is it useful?</p><p><em>Alberto Brandolini</em>: We start by having an unlimited modeling surface at our disposal. The famous “paper roll” serves this purpose. <strong>I cannot possibly model a complex problem within a limited space.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*NoGEOBR1k8CcQ7G1Nqk8eA.png" /><figcaption>Who would have thought orange sticky notes would have ever become so important?</figcaption></figure><p>With a big surface, we can model cooperatively. In order for this to happen we need to <strong>find a common language</strong> allowing everyone to take part in the conversation. A UML (Unified Modeling Language) is not fit for purpose, <strong>Events</strong> work much better.</p><p>At this stage we can <strong>visualize a complex flux</strong> <strong>in a collaborative way </strong>and with the contribution of all experts involved. The events help us <strong>keep the story and the temporal flux consistent</strong>, putting the contradictions of all participants’ points of view under the spot. And… this is useful both for those who need to develop software for a portion of or for the whole business process (because discovering such contradictions well in advance has enormous costs/benefits advantages) and for those who are deeply involved in such processes and know very well a defined portion of the process but not the whole picture.</p><p>In fact we’re using <strong>EventStorming as a tool to design both complex IT systems and the whole services chain with the aim of value generation, comprehension of the ecosystem</strong> and so on.</p><p><em>Avanscoperta</em>: What’s the genesis of the word EventStorming? And also, do you write it as one or two words? :)</p><p><em>Alberto Brandolini</em>: At the beginning I had no strong opinion on this. The first word I used was Event-Based Modeling, which just doesn’t sound right. Then I found out Vaughn Vernon (the author of <a href="https://www.amazon.co.uk/Implementing-Domain-Driven-Design-Vaughn-Vernon/dp/0321834577/ref=sr_1_1?s=books&amp;ie=UTF8&amp;qid=1507645279&amp;sr=1-1&amp;keywords=implementing+domain-driven+design">“Implementing Domain-Driven Design”</a>) had been using the same term to talk about something else, so I had to find a new name.</p><p>A lot of inspiration came from <strong>GameStorming</strong> (which was inspired by brainstorming itself), so <strong>calling it EventStorming was the most natural choice</strong>.</p><p>Without space. Works much better on Twitter! 😉</p><p><em>Avanscoperta</em>: Do you believe it is possible to <strong>apply EventStorming in different industries and contexts</strong>?</p><p><em>Alberto Brandolini</em>: Totally. <strong>We’ve designed startups from scratch, </strong>or we<strong> questioned company policies</strong>.</p><p>We used it to validate a business model and hypothesis of value generation of a company, regardless of a software component being in place. Sometimes we use it as a tool for some <strong>retrospectives</strong>. I’ve tried to use the same approach when <strong>negotiating with my daughter during our “wars of independence”</strong>. And it does work.</p><p><em>Avanscoperta</em>: Your book <a href="https://leanpub.com/introducing_eventstorming">“Introducing EventStorming — An act of Deliberate Collecting Learning”</a> was published in January 2016. Who’s your target reader and what should s/he expect from your book?</p><p><em>Alberto Brandolini</em>: I’m trying to understand it. My target reader is my reader :o)</p><p>I’m quite surprised by the number of people who bought the book betting on the fact I would have been able to put the word “end” to it if I’m honest, so… I couldn’t ask for more! Now I’m being guided by them, with their questions and observations.</p><p><strong>EventStorming was born in the software world, but its utility goes well beyond this realm.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M032r_7mb5NB4h_bimntYw.png" /><figcaption>The self-explaining “picture that explains everything”</figcaption></figure><p>The first readers come from that community. Many of them wear a lot of hats though: they’re very often free thinkers and they’re just “trapped” in a software developer’s body. My challenge is making sure each one of them finds something useful that can help them <strong>solve a problem and do their work in the best possible way.</strong></p><p>In fact I try to explain that developing software is not what we think, there’s a type of recurring problems which cannot be solved in the old way but they can be faced with less conventional tools and instruments. EventStorming is one of them.</p><p><em>Avanscoperta</em>: Ok, I read the book, and then?</p><p><em>Alberto Brandolini</em>: Then you go to the stationery shop, and buy a lot of <strong>orange sticky notes</strong>. But you won’t find them in the area of Faenza, I bought them all :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7P2PDuRVC9MTgiD9GN83_w.png" /><figcaption>Orange is the new… wait, where did we hear it already? :)</figcaption></figure><p>PS. Find out more on <a href="http://www.avanscoperta.it/en/training/eventstorming-master-class-alberto-brandolini/">the next editions of the EventStorming Workshop</a>!</p><p><em>Header image ©</em><a href="https://twitter.com/ddd_eu"><em>DDD Europe</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=97e5d17b5a59" width="1" height="1" alt=""><hr><p><a href="https://medium.com/avanscoperta-we-are-learners/from-ziobrando-to-eventstorming-97e5d17b5a59">From ziobrando to EventStorming</a> was originally published in <a href="https://medium.com/avanscoperta-we-are-learners">Avanscoperta - We Are Learners</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Kingdom of Software]]></title>
            <link>https://medium.com/@avanscoperta/gojko-adzic-and-the-kingdom-of-software-63e1449bd83a?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/63e1449bd83a</guid>
            <category><![CDATA[impact-mapping]]></category>
            <category><![CDATA[product-owner]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Wed, 11 Oct 2017 14:09:13 GMT</pubDate>
            <atom:updated>2017-10-12T08:04:02.617Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GBVJels5ov_cfs2h9wrplg.jpeg" /></figure><h4>Q&amp;A with Gojko Adzic</h4><p><a href="http://www.avanscoperta.it/en/trainer/gojkoadzic/">Gojko Adzic</a> is an award-winning international speaker, consultant, and writer. <strong>One of the most influential personalities in the Agile Testing world</strong>, Gojko wrote renowned books such as “<a href="https://www.amazon.com/Impact-Mapping-Software-Products-Projects/dp/0955683645/ref=asap_bc?ie=UTF8">Impact mapping</a>”, “<a href="https://www.amazon.com/Specification-Example-Successful-Deliver-Software/dp/1617290084/ref=asap_bc?ie=UTF8">Specification by Example</a>” and, most recently, “<a href="https://www.amazon.com/Humans-Vs-Computers-Gojko-Adzic/dp/0993088147/ref=asap_bc?ie=UTF8">Humans VS Computers</a>”. Enjoy this interview!</p><p><em>Avanscoperta</em>: Zdravo, Gojko!</p><p><em>Gojko</em>: Buongiorno!</p><p><em>Avanscoperta</em>: How did you start being interested into software and why?</p><p><em>Gojko</em>: My dad bought <strong>a Commodore 64</strong> when I was 6 years old, and kind of he bought it for himself to tinker with, but to justify the thing (which was quite expensive back then), he told my mum that it was for me. So the computer was officially mine, but because he bought it for himself really, he didn’t buy a cassette unit, so I couldn’t play any games. It took me a year to beg some games out of him, so for the first year the only thing I could do is sit next to him and type over listings from a book into stuff that made the computer make weird sounds or flash things on the screen.</p><p><em>Avanscoperta</em>: Let’s start off with a classic: where do you see software development going?</p><p><em>Gojko</em>: I don’t think it needs to go anywhere, it’s arrived! <strong>Software is now ruling the world</strong>, pretty much software developers now power most of the stuff on the planet.</p><p><em>Avanscoperta</em>: What are the areas where you see the next development happening?</p><p><em>Gojko: …</em></p><h3><strong>Wanna find out more? Head to </strong><a href="http://blog.avanscoperta.it/it/2017/10/12/the-kingdom-of-software-gojko-adzic/"><strong>Avanscoperta’s blog</strong></a><strong> and read the full interview with Gojko!</strong></h3><p><strong>Gojko will be in Bologna</strong> on November 22nd and 23rd to deliver his “<a href="http://bit.ly/Product_Owner_Key_Skills_Gojko_Adzic">Product Owner Key Skills</a>” workshop. Join us for a 2-day event that promises to be legendary with one of the greatest minds in the Agile world.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=63e1449bd83a" width="1" height="1" alt="">]]></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-a22cb412fcb3------2</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>Tue, 09 Aug 2016 12:51:36 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>
        <item>
            <title><![CDATA[Snails for sale: storia di un bambino diventato imprenditore]]></title>
            <link>https://medium.com/@avanscoperta/snails-for-sale-storia-di-un-bambino-diventato-imprenditore-fb6c6811957?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb6c6811957</guid>
            <category><![CDATA[popcornflow]]></category>
            <category><![CDATA[lean]]></category>
            <category><![CDATA[agile-scrum-methodology]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Thu, 23 Jun 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-08-09T12:42:45.353Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*7wf84ANYIhRhZPR2.png" /></figure><h4>Gli esperimenti di Matteo con la PopcornFlow board: un esempio per startup!</h4><p>Matteo ha 7 anni e qualche settimana fa ha deciso di usare PopcornFlow — il metodo ideato da suo padre <a href="https://medium.com/u/9318d3db3de8">Claudio Perrone</a> — per vendere lumache. Sì, avete letto bene, lumache! :)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*aqd6x5hYJVU7Uofu." /></figure><p>Definito il “problema” (provare a vendere lumache), Matteo ha generato 16 opzioni in meno di un’ora e avviato alcuni esperimenti, tra cui: un video su YouTube che spiegasse come nutrire le piccole lumachine e altri consigli utili e segnalare la vendita di lumache.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*yVFkjih8EEVmQQgj." /></figure><h3>1° esperimento</h3><p><strong>Il video tutorial</strong></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F_3Z5FRRnZXs%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D_3Z5FRRnZXs&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F_3Z5FRRnZXs%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/f93c3ee99a945dc50461cc73c4359598/href">https://medium.com/media/f93c3ee99a945dc50461cc73c4359598/href</a></iframe><h3>2° esperimento</h3><p><strong>La segnaletica</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*HAf0EFGAkJoBx-ra." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/16/0*rXh64KOPAFVq4T0J." /></figure><p>Claudio<em>: «Matteo experiments included a “snails for sale” sign on our main door for a week. Don’t you love the typo? “snails for sail” is much more romantic :-)<br>I feel good about this enterprise.»</em></p><h3><strong>I could give up… I’ll never give up!</strong></h3><p>Nonostante i primi esperimenti non avessero portato i risultati sperati, il piccolo Matteo non si è perso d’animo, anzi in brevissimo tempo ha subito avviato una nuova sperimentazione!</p><p>Claudio: «<em>Matteo’s snail adventure is continuing. Here’s a little story he created, in preparation for another experiment he has in mind.»</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FmoGy9mD2BBE%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DmoGy9mD2BBE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FmoGy9mD2BBE%2Fhqdefault.jpg&amp;key=d04bfffea46d4aeda930ec88cc64b87c&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d7fad9fe887715740ce65151a800a1f/href">https://medium.com/media/2d7fad9fe887715740ce65151a800a1f/href</a></iframe><h3>3. esperimento</h3><h4><strong>Il libro a fumetti</strong></h4><p>Claudio:<em> «Oh my… Matteo figured out a way to make money with snails, even if his original ideas bombed.<br>After a couple of decent experiments, Matteo’s snail project took a new exciting turn when he decided to create and sell a snail-themed comic book. He is unstoppable. His story, his drawings.<br>I just setup a donate page for him. He’ll even give 50% of profits to fund the soft-play area in his school.»</em></p><h3><a href="https://popcornflow.com/snails/"><strong>Snail Adventure</strong></a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*FZHkhMJ4WiYqgTU0." /></figure><p><a href="https://popcornflow.com/snails/"><strong>The Snail Comic Book Experiment</strong></a></p><blockquote>I’m “just” a kid and I used PopcornFlow to write a snail comic book as a fun experiment.</blockquote><h3>40 ore dopo…</h3><p>Claudio<em>: «Did even people from the country where the sun was on their side of the earth buy my comic book too???»</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*gTVekuyxGdUCBs8C." /></figure><h3>Claudio Perrone on Twitter</h3><p>Uh? A 7yo Snail entrepreneur? YES! Here&#39;s my kid&#39;s epic #popcornflow story on @slideshare: http://bit.ly/28KTsh9 #leanstartup #innovatio</p><h3>Dublino: <a href="https://twitter.com/coolestprojects">@coolestprojects</a></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/810/0*zl640rYtNXgRf7Xq." /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/16/0*W5K_qr0qyJl4awgU." /></figure><h3>Morale…</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*GVI3EITIdova8dYG." /></figure><p><a href="https://popcornflow.com/">PopcornFlow</a></p><p><a href="http://www.avanscoperta.it/it/training/popcornflow-workshop/">PopcornFlow Workshop in Italy</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb6c6811957" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Lego Matters]]></title>
            <link>https://medium.com/@avanscoperta/why-lego-matters-b4093ce0fa8?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/b4093ce0fa8</guid>
            <category><![CDATA[lego]]></category>
            <category><![CDATA[lego-serious-play]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Thu, 19 May 2016 00:00:00 GMT</pubDate>
            <atom:updated>2016-08-09T12:45:53.113Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KiIbgOMtDKElH4_TY5b-jw.jpeg" /><figcaption><a href="https://www.flickr.com/photos/cocoonprojects/23467349180/in/dateposted/">Foto ©Cocoon</a></figcaption></figure><h3>Madrid, maggio 2011…</h3><p>Siamo a XP2011, una delle edizioni più importanti della <em>XP Conference</em>.</p><p>Tra le tante attività della conferenza, alcuni dei partecipanti sanno che c’è una saletta dedicata in cui sta per succedere qualcosa di importante. <strong>Si parla di fondare quella che poi diventerà ALE</strong> (Agile Lean Europe).</p><p>Entro, ci sono amici, facce conosciute, e facce nuove.</p><p><strong>Jurgen Appelo</strong>, il tessitore della trama di inviti, ci dà il benvenuto. Chiede a tutti partecipanti di mettere un’etichetta sulla maglietta con il nostro nome e la nazione di provenienza. Per qualche motivo ancora misterioso vedo <strong>Jacopo Romei</strong> in rappresentanza della Bulgaria. “Poi ti spiego”.</p><p>La sala è organizzata per tavoli, 6 in tutto. Ad ogni tavolo sono disponibili solo 6 posti. Ci viene richiesto di non avere più di una persona per nazione seduta allo stesso tavolo.</p><p>Mi accomodo, non c’è tempo per le presentazioni. Ed in effetti sono quasi inutili, siamo tutti qui per lo stesso motivo. E tutti distratti dall’<strong>enorme scatola di LEGO® </strong>che campeggia in un angolo.</p><p><strong>Thorsten Kalnin</strong>, il facilitatore della sessione, ci invita a rifornirci di LEGO® e ci concede <strong>15 minuti per costruire un “qualcosa”</strong> che rappresenti quello <strong>che noi crediamo debba essere ALE</strong>, e per spiegarlo ai nostri compagni di tavolo.</p><p><strong>Nei 15 minuti successivi</strong>, ogni tavolo è chiamato a costruire un <strong>singolo artefatto che rappresenti la sintesi</strong> di tutte e sei le posizioni.</p><p><strong>Al terzo round</strong>, con gli ultimi 15 minuti a disposizione, ogni tavolo è chiamato a scegliere un proprio delegato per il tavolo finale, che andrà a <strong>creare una sintesi di tutte le posizioni</strong>, in un unico artefatto, che poi dovrà essere illustrato a tutti.</p><p>La descrizione dell’artefatto viene filmata (il video è disponibile <a href="https://www.youtube.com/watch?v=Zg2PMv8lFUA">qui</a>). Tutti dichiarano di sentirsi rappresentati, e <strong>firmano solennemente un quaderno</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/222/0*IWzOXHFdLiccsoKy.jpg" /></figure><p><a href="http://alenetwork.eu/">Agile Lean Europe</a> è stata ufficialmente fondata.</p><p><strong>In soli 55 minuti</strong>.</p><p>Da persone che non si conoscevano, che non hanno avuto il tempo di presentarsi, e che sono uscite dalla stanza dopo aver raggiunto una visione condivisa.</p><p><strong>In 55 minuti</strong>.</p><p>3 mesi dopo a Berlino, dal 7 al 9 settembre 2011, ha luogo la prima edizione di Agile Lean Europe, quella che per me resta una delle migliori formule di conferenze in assoluto. Il dado è tratto.</p><p><strong>Ribadisco, 55 minuti.</strong></p><p>Una tipica riunione di 36 persone, in 55 minuti riesce a malapena a raccogliere tutti i partecipanti, a fare qualche presentazione, e ad annoiarli con qualche preambolo. Qui sono riusciti a mettere insieme gente che non si conosceva, di nazioni diverse e a raggiungere un accordo su qualcosa di nuovo in 55 minuti.</p><p>C’è qualcosa di grosso, che ancora mi sfugge.</p><h3>Colline Umbre, maggio 2011…</h3><p>Siamo alla prima edizione dell<strong>’Agile Coach Camp</strong>. Tra le varie sessioni, partecipo ad una <strong>piccola introduzione a LEGO® SERIUOS PLAY®</strong>.<br> Julie, che facilita la sessione, ci fa cominciare con qualcosa di semplice: costruire una piccola tartarughina.</p><p>Poi ci chiede di personalizzarla, aggiungendo qualcosa che ci rappresenta, e di spiegare il perché.<br> E qui mi rendo conto che comincio a parlare di me, dicendo a persone appena conosciute, cose che non ho mai detto neanche ad amici di vecchia data.</p><p>Al terzo giro, ci chiede di rappresentare perché siamo lì e che cosa ci aspettiamo da questo Coach Camp. In questo caso <strong>la spiegazione dei simboli è più complessa</strong>: mi sono rappresentato come un omino sceso da cavallo, che ora procede a piedi come tutti gli altri.<br> Il significato è che una cosa è l’immagine che il mercato ci costringe a dare, quella dell’esperto, un’altra è la necessità di mettersi in gioco e di imparare, e di dichiararsi principiante. Di fatto prendo l’impegno di dedicarmi alle sessioni su temi in cui sono più ignorante, rispetto a quelle dove potrei più facilmente “dire la mia”.</p><p>Ok, di nuovo mi trovo a confidarmi con persone che ho appena conosciuto, ed a prendere un impegno. <strong>C’è qualcosa di decisamente interessante nel modo in cui LEGO® permette di superare certe difese</strong>.</p><p>La sessione termina, mentre Julie ci fa presente che il vero LEGO® SERIOUS PLAY® è molto più profondo, e qui stiamo solamente grattando la superficie.</p><p>Il problema è quello che succede il giorno seguente.</p><p>La mattina dopo, apro gli occhi e WOOOM! <strong>La prima cosa a cui penso è il cavallo di LEGO®</strong> <strong>e la mia intenzione che ho dichiarato ai partecipanti del workshop</strong>.</p><p>Non l’ho solo dichiarata. Ho la sensazione di avere promesso qualcosa, o meglio, di aver preso un impegno solenne davanti a me e davanti agli altri.</p><p>Le parole pronunciate illustrando quel <em>rozzettino</em> di LEGO® per me avevano avuto lo stesso valore di un giuramento solenne pronunciato tenendo il Graal fra le mani.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*2WtV79KX3lXPL96Y.jpeg" /></figure><p>In quel momento ho cominciato a capire quale fosse la <strong>reale potenza dei LEGO®</strong>, e quali canali riuscissero ad attivare nel cervello.</p><h3>Enter LEGO® SERIOUS PLAY®</h3><p>A questo punto incomincio a studiare, e a documentarmi. <strong>Comincio anche a pensare ai LEGO® come strumento di modellazione</strong>.</p><p>Grazie a Jacopo Romei entro quindi in contatto con <strong>Stelio Verzera</strong> che già da tempo, stava esplorando il territorio LEGO® SERIOUS PLAY® (il sito di <a href="http://cocoonprojects.com/it/">Cocoon Projects</a> non è un capriccio nerd, ma una precisa dichiarazione di intenti).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/0*uDHae9usE0ahhpSR.jpg" /></figure><p>E scopro che c’è una storia non da poco dietro i LEGO® e soprattutto dietro al concetto diLEGO® SERIOUS PLAY®. E che solo poco di quella storia traspare dietro alle <a href="http://www.lego.com/en-us/seriousplay/background">fonti ufficiali</a>.</p><p>Scopro che la gestazione del “prodotto” LEGO® SERIOUS PLAY® è stata lunga e complicata, principalmente perché c’era la consapevolezza di avere a che fare con <strong>qualcosa di estremamente potente</strong>, ma anche da maneggiare con estrema accortezza.</p><p>Rispetto ad altre modalità di workshop, <strong>LEGO® SERIOUS PLAY® ha infatti la capacità</strong> — sfruttando il principio del pensare con le mani — <strong>di attivare livelli di introspezione normalmente inavvicinabili</strong>, permettendo di arrivare estremamente in profondità, e di fare emergere le motivazioni, anche inconsce, dentro di noi.</p><p><strong>Questa potenza introspettiva va gestita</strong>, perché può risultare pericolosa, o fare emergere situazioni difficili da gestire senza la <strong>guida di un facilitatore esperto</strong>. Allo stesso modo, se correttamente incanalata può dare risultati incredibili, perché <strong>permette di allineare obiettivi razionali con quelli più profondi</strong>, con risultati e conseguenze che nella nostra normale esperienza lavorativa sono un miraggio.</p><h3>Tutti parlano di LEGO®</h3><p>Negli ultimi 2 anni il tema è finalmente esploso.<strong> Chi ha provato l’esperienza con i LEGO® non è riuscito più a trattenersi dallo spargere la voce e dal diffondere la buona novella</strong>.</p><p>Ed abbiamo visto tante variazioni sul tema dei LEGO® portare risultati interessanti. <strong>I LEGO® sono strumenti potenti da usare come esempi e come metafore</strong>.</p><p>Il <a href="http://www.agile42.com/en/blog/2011/12/25/cynefin-lego-game/">Cynefin LEGO® Game</a>, per citarne uno, è un esempio spettacolare di uso dei LEGO® a supporto di un processo di apprendimento, perché il gioco mette il cervello in uno stato mentale perfetto per imparare nuove cose (in questo caso il Cynefin Framework ed il comportamento nei sistemi complessi, <em>hai detto niente</em>).</p><p>Ma anche se è un gioco, e se è serio perché utilizzato in un contesto business, non è LEGO® SERIOUS PLAY®.</p><p><strong>Quando parliamo di LEGO® SERIOUS PLAY® parliamo di una serie di pratiche certificate</strong>, che portano le persone a ‘pensare con le mani’ a riflettere in gruppo ed ad aprire porte che normalmente restano chiuse.</p><p><strong>Quando parliamo di LEGO® SERIOUS PLAY® parliamo di persone che hanno compiuto un processo di perfezionamento lungo e complesso</strong>, per poter essere in grado di gestire le situazioni che possono venirsi a creare nel corso di un workshop.</p><p><strong>Quando parliamo di LEGO® SERIOUS PLAY® parliamo di uno strumento in grado di scavare nel profondo</strong>, con tutto quello che ne consegue, sia in termini di potenzialità che di rischi.</p><h3>E da ora ne parliamo anche noi</h3><p>Come tanti altri temi che trattiamo, <strong>LEGO® SERIOUS PLAY® è uno strumento potente, che funziona e che permette di risolvere alcuni blocchi ricorrenti</strong> sia nel mondo dello sviluppo software, che nelle trasformazioni aziendali.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/0*3AmKuvBJXRi-118K.jpg" /></figure><p>Partendo da due di questi problemi, la corretta <strong>definizione di un prodotto/servizio in linea con le reali aspettative degli utenti e la risoluzione degli annosi conflitti sulla linea di confine tra sviluppo e management</strong>, andiamo a proporre i primi due titoli su questo tema:</p><p>Aspettatevi sorprese! 😉</p><p><em>Originally published at </em><a href="http://blog.avanscoperta.it/it/2016/05/19/perche-lego-serious-play/"><em>blog.avanscoperta.it</em></a><em> on May 19, 2016.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b4093ce0fa8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cosa c’entra Kanban con la Piadina Romagnola]]></title>
            <link>https://medium.com/@avanscoperta/cosa-centra-kanban-con-la-piadina-romagnola-bfdfe45d3dd4?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/bfdfe45d3dd4</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[kanban]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Mon, 16 Mar 2015 00:00:00 GMT</pubDate>
            <atom:updated>2016-08-09T12:46:31.119Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZZY1xePU8KEyQwxQ.jpg" /></figure><p>Uno dei princìpi che pervade trasversalmente l’intera offerta di Avanscoperta è vedere <strong>la formazione dal punto di vista del cliente</strong>, piuttosto che dal punto di vista del formatore.<br> Ogni volta che progettiamo un corso o ci viene richiesta una consulenza cerchiamo di<strong> progettare l’esperienza formativa in modo da massimizzare le probabilità di comprensione da parte dello <em>studente</em></strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*v0K3Id9ombjQHrio.jpg" /></figure><p>Uno degli strumenti che usiamo per raggiungere questo scopo è <strong>la progettazione e l’utilizzo di giochi come strumenti di comprensione</strong>.</p><p>Da qui nasce quello che noi candidiamo ad essere il quinto principio del <a href="http://www.agilemanifesto.org/iso/it/">Manifesto Agile</a>:</p><blockquote><strong><em>L’apprendimento vince sull’insegnamento.</em></strong></blockquote><p>Per approfondire perché il gioco è importante ed estremamente efficace, ti suggeriamo queste letture:</p><ul><li><a href="http://www.gamestorming.com/">Game Storming</a></li><li><a href="http://www.impactmapping.org/">Impact Mapping</a></li></ul><p>E anche noi stiamo esplorando alcuni strumenti!</p><h4>Kanban Pizza Game</h4><p>Una delle cose che più spesso ci troviamo a dover spiegare è che cosa sia <a href="http://www.avanscoperta.it/it/training/kanban-software-development/">Kanban</a>, come funziona, da dove si inizia.<br> Conosciamo ad oggi diversi giochi e simulazioni che ci aiutano in questo, ma ci piace anche sperimentare e trovarne di nuovi, perché avere un unico strumento per ogni problema sarebbe come usare solo la forchetta per ogni tipo di piatto. Questo ci renderebbe meno efficaci nei confronti di chi dobbiamo aiutare.</p><p>Abbiamo sentito parlare (e in parte l’abbiamo visto all’opera) di <a href="http://www.agile42.com/en/training/kanban-pizza-game/">Kanban Pizza Game</a>, ideato e progettato da Agile42, nostri competitor ma anche nostri amici! :)</p><p>La documentazione di <strong>Kanban Piazza Game</strong> è fatta talmente bene che vi rimando al loro sito. Ci sono tutte le informazioni che vi permettono di poterlo replicare nella vostra azienda, a patto che si rispettino determinate condizioni.</p><h4>Da Romagnoli preferiamo la piadina!</h4><p>Perché <em>Pizza</em>?<br> Nel loro sito i ragazzi di Agile42 spiegano che “<em>We think that the idea of using paper pizza is great — everybody loves pizza, and everyone knows how a pizza is made (at least in general terms)”.</em></p><p>Ma noi siamo romagnoli! Quindi perché non provare a declinare Kanban Game nel nostro contesto, nel nostro territorio?</p><p>Ecco il primo esperimento di<strong> Kanban Piadina Game</strong> in Avanscoperta!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*rmpMc_0y5VQNY0Ug.jpg" /></figure><h4>Fare, riflettere, iterare</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*Jci6cD1Os27ZWMtz.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZV65xATxXuXsdNZ7.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/768/0*ZubiysEbU0yx_rla.jpg" /></figure><h4>Conclusioni</h4><p><strong>Kanban Piadina Game</strong> si è dimostrato un ottimo gioco per spiegare i princìpi di Kanban.</p><p>Abbiamo notato anche alcuni piccoli limiti (come ad esempio il numero minimo di persone), nonostante questo è diventato per noi un tool prezioso.</p><p>Grazie ai ragazzi di Agile42 per averlo ideato!</p><p>Ricambieremo presto il favore… 😉</p><p>Risorse utili</p><ul><li><a href="http://www.agile42.com/en/training/kanban-pizza-game/">Kanban Pizza Game</a></li><li><a href="http://tastycupcakes.org/?s=kanban&amp;x=0&amp;y=0">Elenco di giochi per spiegare Kanban</a></li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/470/0*4b39VCGFC2etnCgd.jpg" /></figure><p><em>Originally published at </em><a href="http://blog.avanscoperta.it/it/2015/03/16/kanban-game-e-la-piadina-romagnola/"><em>blog.avanscoperta.it</em></a><em> on March 16, 2015.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bfdfe45d3dd4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing EventStorming]]></title>
            <link>https://medium.com/@avanscoperta/introducing-eventstorming-ea60b03671bc?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea60b03671bc</guid>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Wed, 12 Feb 2014 00:00:00 GMT</pubDate>
            <atom:updated>2016-05-31T13:05:01.034Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Xy1ubI7eMrkDLRRL.jpg" /></figure><p>In the past months I’ve spent some time experimenting with this weird thing. It started like a <em>“Ouch I have no time to draw a precise UML diagram, let’s do this instead” </em>then became a thing called Event-Based modelling workshop that I presented at Italian Agile Day 2012, I later had the chance to do more experiments in Belgium and Poland during Vaughn Vernon’s IDDD tour, and I gathered incredibly valuable feedbacks and insights. I managed to find a cooler name — <strong>EventStorming</strong> — just before the whole thing exploded in summer 2013. While I realised there was a lot of value in it, other practitioners (<a href="http://verraes.net/2013/09/dddbe-modellathon/">Mathias Verraes</a>, <a href="http://tojans.me/blog/2013/09/04/the-very-first-dddbe-event-the-modellathon/">Tom Janssen</a>, <a href="http://www.heimeshoff.de/wordpress/?p=276">Marco Heimeshoff</a>, Yves Reynhout,<a href="http://www.meetup.com/DDD-Paris/events/142503812/"> Tomas Jaskula</a>, <a href="http://bettercoderwannabe.blogspot.it/2013/09/first-event-storming-experiment.html">Alessandro Colla</a>, Andrea Balducci,<a href="http://www.jefclaes.be/2013/11/event-storming-workshop-slides.html"> Jef Claes</a>, just to name a few) started exploring and playing with the format with amazing results, leading me to the conclusion that this is something more than “just another workshop format”.</p><h3>What is Event Storming</h3><p>Event Storming is <strong>a workshop format for quickly exploring complex business domains</strong>.</p><ol><li>It is powerful: it has allowed me and many practitioners to come up with a comprehensive model of a complete business flow in hours instead of weeks.</li><li>It is engaging: the whole idea is to bring people with the questions and people who know the answer in the same room and to build a model together.</li><li>It is efficient: the resulting model is perfectly aligned with a Domain-Driven Design implementation style (particularly fitting an Event Sourcing approach), and allows for a quick determination of Context and Aggregate boundaries.</li><li>It is easy: the notation is ultra-simple. No complex UML that might cut off participants from the heart of the discussion.</li><li>It is fun: I always had a great time leading the workshops, people are energised and deliver more than they expected. The right questions arise, and the atmosphere is the right one.</li></ol><p><a href="http://ziobrando.blogspot.it/2013/11/introducing-event-storming.html"><strong><em>Read the full post on ziobrando’s Blog</em></strong></a></p><p><em>Originally published at </em><a href="http://blog.avanscoperta.it/it/2014/02/12/introducing-event-storming/"><em>blog.avanscoperta.it</em></a><em> on February 12, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea60b03671bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Benvenuti in Avanscoperta]]></title>
            <link>https://medium.com/@avanscoperta/benvenuti-in-avanscoperta-2673e57c990e?source=rss-a22cb412fcb3------2</link>
            <guid isPermaLink="false">https://medium.com/p/2673e57c990e</guid>
            <category><![CDATA[medium-italia]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Avanscoperta]]></dc:creator>
            <pubDate>Sat, 01 Feb 2014 00:00:00 GMT</pubDate>
            <atom:updated>2016-05-31T12:59:57.876Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WVhw9wpms006tlHE.jpg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/126/0*7Ai4BhhSeCR310ys.png" /></figure><p>Il blog di Avanscoperta è lo spazio per gli aggiornamenti sulla nostra attività di formazione.</p><p>Qui troverete articoli di approfondimento sugli argomenti trattati nei nostri workshop, <em>guest post</em> e <em>Q&amp;A</em> con i nostri docenti.</p><p>Perché anche questo possa essere un luogo di apprendimento e di scambio di spunti, esperienze, idee e informazioni.</p><p><strong>Benvenuti!</strong></p><p><em>Originally published at </em><a href="http://blog.avanscoperta.it/it/2014/02/01/benvenuti/"><em>blog.avanscoperta.it</em></a><em> on February 1, 2014.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2673e57c990e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>