<?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 Tim Duehrkoop on Medium]]></title>
        <description><![CDATA[Stories by Tim Duehrkoop on Medium]]></description>
        <link>https://medium.com/@tdu?source=rss-1a52234f039e------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*w3n-kE2BYeBlxltq.jpg</url>
            <title>Stories by Tim Duehrkoop on Medium</title>
            <link>https://medium.com/@tdu?source=rss-1a52234f039e------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 14:06:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@tdu/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[Distributed Agile: Video, beer gardens and stuffed animals]]></title>
            <link>https://medium.com/@tdu/distributed-agile-video-beer-gardens-and-stuffed-animals-5bf51136d5d8?source=rss-1a52234f039e------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bf51136d5d8</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[social-trust]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[distributed-teams]]></category>
            <category><![CDATA[productivity]]></category>
            <dc:creator><![CDATA[Tim Duehrkoop]]></dc:creator>
            <pubDate>Fri, 27 Dec 2019 11:14:13 GMT</pubDate>
            <atom:updated>2019-12-27T11:14:13.141Z</atom:updated>
            <content:encoded><![CDATA[<p>The sixth of the twelve <a href="https://agilemanifesto.org/principles.html">principles of agile software development</a> reads</p><blockquote>The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.</blockquote><p>While this is definitely true, real-world agile projects often take place with people in multiple locations. People prefer to work from home or want to avoid grinding commutes, project stakeholders are based in different locations, service providers have the right experts in different offices. Bringing everyone into the same place every week is also not a good option: travel is expensive, disruptive to life and not good for the climate.</p><p>So how can we still enable efficient and effective information transfer, and the social trust within a team that makes it work as a team?</p><p>The good news is that much has changed since the Agile Manifesto was written in 2001. Desktop video is now a reliable, high quality technology supported by sufficient connection speeds in most places, conference audio is reliable and cheap as well. Also, there is growing understanding for agile ways of working, for the productivity gains that can be achieved with agile software development.</p><p>At <a href="http://www.namics.com/">Namics</a>, we have run large-scale agile development programs with distributed teams for many years now. Here are some elements that make Distributed Agile successful in our experience:</p><ol><li><strong>Have everybody on video, all the time. </strong>When doing one-on-one meetings or bigger events, it helps seeing people’s faces. This means that more information is conveyed in a meeting, and it also works against the temptation to multitask.</li><li><strong>Have regular in-person meetings. </strong>In a highly distributed, long-running project with a German client, we have done quarterly in-person sprint changes for four years now. All key sprint events for that particular sprint change (review, planning, retrospective) are carried out on-site at the client’s offices. In the evening, a social event takes place, with food and drink, in a beer garden in summer, and with foosball and ping-pong tournaments. All team members and project stakeholders are invited, bringing the total to around 50 at each of the evening events, and enabling plenty of random interactions among the team members.</li><li><strong>Use supporting software for the remote interactions. </strong>For a retrospective, it can be sufficient to have everybody write into the same structured Google slide. More elaborate tools also have their place. Most important: Always think about how the experience of participating in a meeting is engaging and rewarding for all participants.</li><li><strong>Have a mascot. </strong>The project described above was initially code-named Chameleon, so we got everybody two toy Chameleons — one small travel version, and a bigger one to keep around the desk. Chameleons travel the world, are put in photos, and show up regularly on team calls, creating a sense of connectedness throughout the highly distributed team.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ekiv2eW88zNsdl12" /></figure><p>So is this all about fun and happiness? Not at all! In our experience, joy and social trust are strong determinants of team performance, and, thus productivity. Using video instead of voice calling (or, even worse, email or task trackers such as Jira or TFS) keeps the social trust going for longer, without expensive, unproductive travel.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*TmkCi2SswEq4Oefg" /></figure><p>Interestingly, investing modest amounts into desktop video infrastructure (essentially a couple of webcams and conference speakers), and reserving a travel budget for a regular get-together of the team can be surprisingly hard. Much harder in fact than justifying a budget for full presence of the team at the client’s site. So be prepared to argue the case, argue that saving big on travel and increasing productivity is possible today if everybody is willing to go “full agile” and create the necessary environment for it in a remote setting.</p><p><strong>So as I dare to contradict the Agile Manifesto regarding the Face-to-Face requirement, I encourage you to dare and try it out for yourself! Just create the necessary conditions around it for fun and joy, and thus, social trust and productivity.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bf51136d5d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>