<?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[Francesco Fucci - Medium]]></title>
        <description><![CDATA[System engineer and developer, music geek - Medium]]></description>
        <link>https://medium.com/francesco-fucci?source=rss----6a87905857d---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>Francesco Fucci - Medium</title>
            <link>https://medium.com/francesco-fucci?source=rss----6a87905857d---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 00:28:49 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/francesco-fucci" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Being Agile When Everyone Is Not]]></title>
            <link>https://medium.com/francesco-fucci/being-agile-when-everyone-is-not-6e370cd278f5?source=rss----6a87905857d---4</link>
            <guid isPermaLink="false">https://medium.com/p/6e370cd278f5</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[experience]]></category>
            <category><![CDATA[prototyping]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Francesco Fucci]]></dc:creator>
            <pubDate>Tue, 21 Nov 2017 20:51:24 GMT</pubDate>
            <atom:updated>2017-11-22T09:44:50.329Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vLtFVPTHJGDfw3XOl4C1Sw.jpeg" /><figcaption>(Photo by <a href="https://unsplash.com/photos/bq31L0jQAjU?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">“My Life Through A Lens”</a>)</figcaption></figure><p>Thinking that actual coding and system prototyping is not important when designing and developing complex systems is in my view the way to make system development more expensive than it actually should be.</p><p>Being in contact with several departments in a big organization, taught me that , most of the time, the main problem is the lack of communication between the people,the technology and processes are just byproducts of communication. That is why too many documents and documents review are ways to make the system design process more ambiguous. Prototype as documentation could be a way to show that ideas work on the real deployed system, especially when systems are cutting-edge and then designers do not really know all the subtle issues covered by documents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gGctmR-8lU5n-4-KhThc4w.jpeg" /><figcaption>Software developers and communication (Photo by <a href="https://unsplash.com/photos/gA-vxrqmYV8?utm_source=unsplash&amp;utm_medium=referral&amp;utm_content=creditCopyText">Sérgio Rola</a>)</figcaption></figure><p>When many people do not communicate through well defined channels is really hard to keep track of the progresses at a higher management level, which makes also hard to define short-term goals on project, especially when these projects last for several decades. The greater is the number of people involved in a project, the harder becomes to manage the communication between them. Most of my time has been spent in communicating with people via document reviews and long e-mails, when it would be a lot more productive report the challenges through practical examples produced via artifacts, just to try to get close as possible to the final product through many prototypes design.</p><p>In this case, the “divide et impera” principle is more than ever important, because most of the time problem can be solved quickly from a technological side when the system is well “modularized”. What I mean with “modularization” is to find the <strong>right</strong> interface set of functionalities which the designer selects and then marks as module. The choice of these functions depends on the on-field experience of the designer. Such experience is correlated with the time that the designer spent on the issues of that particular domain.</p><p>I achieved a successful result on a system engineering project by trying to get my hands dirty on the code as soon as I could. At the beginning the phases and the procedures were not so clear in my mind. I just wanted to get a first result (by hacking :) ) and see something coming.</p><p>Then, I stopped for a while, assessing what I really learnt by that burst, focusing on the challenges I faced writing the code to solve that a specific problem and then trying to generalize it. I found many flaws that I could have never found with just documents. I also helped people working with me in understanding what I had in mind. On the other hand, they also helped me to improve the product and my workflow. In my mindset, I saw that prototyping is the only way of really understanding the flaws of my solution, and the way to find better strategies to make good tools for control system designers.</p><p>What I think is that be quick does not mean be agile. Trying to solve something quickly helped me to develop a more robust and adaptative workflow though. Agile it means, to apply a workflow which is consolidated via on-field experience and success. Designers trust reliability in workflow, which means find both the right number of stages and the right complexity for each stage.</p><p>My hint is to build things as soon as possible and then communicate with stakeholders and your peers via the produced artifacts and real prototypes.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e370cd278f5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/francesco-fucci/being-agile-when-everyone-is-not-6e370cd278f5">Being Agile When Everyone Is Not</a> was originally published in <a href="https://medium.com/francesco-fucci">Francesco Fucci</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>