<?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 Simon Spielmann on Medium]]></title>
        <description><![CDATA[Stories by Simon Spielmann on Medium]]></description>
        <link>https://medium.com/@simon.spielmann?source=rss-76ca218ff95c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*MrZEnkXu7Uf5nbk63owm3g@2x.jpeg</url>
            <title>Stories by Simon Spielmann on Medium</title>
            <link>https://medium.com/@simon.spielmann?source=rss-76ca218ff95c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:48:13 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@simon.spielmann/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[Virtual Feature Teams in Semi-Agile Environments]]></title>
            <link>https://medium.com/@simon.spielmann/virtual-feature-teams-in-semi-agile-environments-d13b10afd888?source=rss-76ca218ff95c------2</link>
            <guid isPermaLink="false">https://medium.com/p/d13b10afd888</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[capgemini]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[development]]></category>
            <dc:creator><![CDATA[Simon Spielmann]]></dc:creator>
            <pubDate>Sat, 20 Nov 2021 09:45:06 GMT</pubDate>
            <atom:updated>2021-11-20T13:13:20.370Z</atom:updated>
            <content:encoded><![CDATA[<p>Today working in an agile product-centric teams is highly recommended in software engineering. But you will sometimes realize that this ambition is not really feasible for the given context. The architecture isn’t made of microservices or self-contained systems of reasonable size, but the product to develop is a large at best modulithic beast, which requires dozens of developers. Furthermore, overall government may discourage the setup of really “integrated” agile teams. E.g., an existing test team with its own steering is still commonly found in practice.</p><p>In such environments “virtual feature teams” are a real-world proven approach, which allows you to leverage agile benefits in a non- or semi-agile environment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*RUpKb2MN5QFvEPVf" /><figcaption>Photo by <a href="https://unsplash.com/@cwmonty?utm_source=medium&amp;utm_medium=referral">Chris Montgomery</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h3>Virtual Feature Teams along the Software Development Lifecycle</h3><p>To explain how virtual feature teams work we need an understanding of the underlying software development lifecycle. So, let’s have a look at the following simplified process:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/744/1*cdGhsNpOwCHj4HEaI9xl9A.png" /></figure><p>Each sprint consists of three phases. The shown phases do not mean long periods of time, but naturally things must be done in a specific order. Before implementation can be done there needs to be a describition of what to implement. Thats what we call “spec” in the picture above. For virtual feature teams to work it is not important whether it’s full fledge specification documents or user stories. Afterwards the feature can be implemented and tested. For sure these activities may overlap and don’t have to be of equal length as in the picture above.</p><h3>What is a Virtual Feature Team?</h3><p>The basic idea is quite simple. In your whole team there are business analyst, developers, and testers. But you do not treat them as separate teams. Instead, you build teams per feature across these professions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/1*ECg2wwuLs_Lbyal_GySl6Q.png" /></figure><p>The virtual feature team has end-2-end responsibility for specifying, implementing and testing its feature. For sure it cannot bring it’s feature into production alone and must sync with the other feature teams. It is also possible to give two or more similar features to one team. But the setup lasts only for one sprint.</p><h3>How are Virtual Feature Teams working?</h3><p>In virtual feature teams responsibilities and focus changes along the software development lifecycle.</p><h4>Specification</h4><p><strong>During specification the business analyst in the virtual feature team has the lead</strong>. The business analyst is responsible for writing user stories. He or she actively gathers feedback from the developers to assure that the story is technically feasible and understandable for the developers. He is also in contact with the testers to assure the tests know what will come and they understand the story also. Therefore the analyst should setup a regular meeting to synchronize work in the team.</p><p><strong>The developers support the business analyst.</strong> They focus on the more technical aspects of a story, for instance performance-aspects, defined error-handling and so on. The developers are also responsible for estimating the implementation work.</p><p><strong>The testers support in preparing acceptance criteria</strong> for the feature and should start with test preparation. This includes gathering of testing ideas and assuring that everything is in place for later testing — prepare test data, test mocks and so on.</p><h4>Implementation</h4><p><strong>When the user story is ready the developers take the lead</strong>. It is quite natural that more than one developer is required for a feature. You maystart with just one developer who supports during specification and let other developers join the team later. The developers start implementing the feature. Whenever something is testable the developers hand it over to the testers, so they can begin testing as soon as possible.</p><p><strong>The business analysts support the developers (and testers) in answering detail questions on how the feature should work. </strong>It may also happen that some edge cases must be decided, which were not mentioned in the story yet.</p><p><strong>The testers focus on preparing test cases and start testing parts of the features</strong> whenever something is ready for test.</p><h3><strong>Test</strong></h3><p>During test the testers take the lead. They test the features and create bug reports. The developers are in charge of bugfixing and supporting the testers. The business analysts support the developers (and testers) in answering detail questions.</p><h3>Why should I do it?</h3><p>I saw virtual feature teams working very well in practice. I think it is worth trying if the circumstances match:</p><ul><li>Agile transformation not (yet) finished</li><li>Mono- or Modulithic architecture</li><li>Stories or Work-packages in varying size</li></ul><p>With virtual feature teams you gain end-2-end responsibility in each team. Especially compared to business analyst, developer and test teams working in dedicated teams in silos.</p><p>Compared to fixed semi-agile teams you avoid knowledge islands and drifting apart processes. Since each team is setup per feature it is also very easy to adapt the team size to the feature size.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d13b10afd888" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>