<?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 Michael Lindemeier on Medium]]></title>
        <description><![CDATA[Stories by Michael Lindemeier on Medium]]></description>
        <link>https://medium.com/@michael.lindemeier?source=rss-f20e7de72729------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8huOO5COxgv-SFYGvIlVuQ.png</url>
            <title>Stories by Michael Lindemeier on Medium</title>
            <link>https://medium.com/@michael.lindemeier?source=rss-f20e7de72729------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 18:08:52 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@michael.lindemeier/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[Our first take on cross-functional teams]]></title>
            <link>https://stories.celebrate.company/our-first-take-on-cross-functional-teams-b0af5476d802?source=rss-f20e7de72729------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0af5476d802</guid>
            <category><![CDATA[cross-functional]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[tech]]></category>
            <dc:creator><![CDATA[Michael Lindemeier]]></dc:creator>
            <pubDate>Wed, 26 Oct 2016 11:45:34 GMT</pubDate>
            <atom:updated>2018-08-22T14:29:39.581Z</atom:updated>
            <content:encoded><![CDATA[<p>When we started to source-in our development efforts in 2012 we had a simple situation, besides the obvious hassle to discover and convince talent to join our then small company. <a href="https://medium.com/u/cb39e0d25146">Christoph</a> and <a href="https://medium.com/u/7209143c87fd">Steffen</a> decided on what to build and its priority. They were also in constant and direct exchange with our development team of 3ish developers. When the team began to grow, we started our first move towards scrum with all the typical problems and advantages in the beginning.</p><p>In the last 24 months, our dev team grew to over 20 developers, QA and technical product managers and with that new problems arose. The expected increase in output was eaten alive by more and more inefficient meetings and growing communication overhead. The result were unhappy developers and unhappy stakeholders. Our main problems were</p><ul><li><strong>Increasingly inefficient meetings</strong><br>Have two people in a planning and everything said concerns both participants. With a growing amount of people there is more unimportant information for everyone. The alternative is, people talk less detailed about issues worth discussing. This applies to plannings, stand-ups, retrospectives and many more.</li><li><strong>The one big project blocks everything else</strong><br>As we basically have one development team, we try to focus on one project at a time. Therefore big projects block the development team for quite a long time and delay other projects. This leaves no room for smaller projects.</li><li><strong>Everything else delays the one big project</strong><br>Even though we tried to keep the focus for the development team clean on one topic, there are always urgent issues (production issue, live bugs, order problems) that we have to take care of with high priority. As this is unpredictable it makes planning on the prioritized issues quite hard.</li><li><strong>Crazy knowledge silos</strong><br>We had very few people who knew a lot about our systems. Therefore they were constant bottle necks for questions, implementations and bugfixes.</li></ul><h3>So, how did we tackle this?</h3><p><strong>1. Work in parallel!</strong></p><p>First we took care of the team size. We decided to head to cross functional teams with a size of about 6 people consisting of frontend and backend developers, QA and a technical product manager which is basically a traditionally setup for a team in a “scrumish” development process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/694/0*VIRKuY2FF5F-1eHx." /><figcaption>Our current team setup.</figcaption></figure><p>Breaking down the big team into several smaller teams already offers quite a lot of solutions for the problems we were facing. On the one hand it is quite obvious that all the meetings like stand-ups, plannings, groomings etc. are faster and more relevant for everyone. Additionally we have multiple teams we can assign projects to and work on topics in parallel.</p><p>To be even more flexible when it comes to assigning issues and projects to teams, we consciously decided to not set any technically focus for teams. Meaning, every team should be able to work on any kind of topic, enabling us to assign a prioritized issue to the very next team available. Being saddled by our knowledge silos before, this was very important for us.</p><p><strong>2. Split daily requests from bigger issues on our roadmap</strong></p><p>In a second step we took care of managing the inflow. As noted before we started with some kind of a “top down” prioritization of new features and projects. Besides that we had to handle smaller requests with different urgencies like new card formats, order problems and bugs which we did not want to queue in behind big and long going projects.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*O32E9JzdLCC70CSf." /><figcaption>The separation of issues is done by the approx. size where small issues (&lt; 1 day of implementation) go to our “Daily Requests” board.</figcaption></figure><p>We introduced a “2 stream” roadmap process where we distinguished between (larger) roadmap issues which could be new functionalities, complete system replacements or other stuff that takes quite a long time to investigate and implement. On the other hand, we have smaller “daily” requests that are fast to develop and usually high in priority.</p><p>We then gave the teams a regular sprint to work on roadmap projects without being interrupted by daily stuff. Additionally we blocked a day between two sprints where all teams focussed on the smaller issues only. The daily requests are prioritized by the product management directly. For transparency and alignment purposes the prioritization of the roadmap is done with all relevant stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*QcjWBYBE7XLvV09M." /><figcaption>We have one dedicated day to work on “no-sprint related” stuff.</figcaption></figure><p>This way we can still assure a fast time-to-market for smaller issues and at the same time the teams can focus on the roadmap issues within a sprint.</p><h3><strong>How has it worked out?</strong></h3><p>We have been working in the new setup for about 6 month now and that makes it a good time for a first summary on what we have learned so far:</p><p><em>1. The benefits of small teams!</em></p><p>The quite obvious aspects of of having smaller teams work out as expected. We have more effective and efficient stand-ups, retrospectives, groomings and plannings which leads to less waste of time and more motivated people (nobody likes meetings). Besides the fact that we can now work on stuff in parallel we definitely get more stuff done simply because of two facts:</p><p>The smaller teams can work closer aligned and focus on their own sprint goal as they are not being distracted by other (daily request) issues or the overhead you get when you simply have too many cooks spoiling the broth.</p><p>On top of that we can now easily locate a whole team in one room which lead to an improvement of team spirit and communication.</p><p><em>2. Alignment between the teams!</em></p><p>One thing we thought of to be challenging when splitting the teams was to keep the teams aligned and informed. As we did not assign any system to a team we have teams working in the same repositories at the same time and we still have to keep all team members up to date about new features and implementations. The only constraint we gave was that code reviews should be done cross-team and relied on the communication of the frontend, backend and TPM team to be enough to get everyone informed. And what can we say? That works pretty well so far.</p><p><em>3. Scalability!</em></p><p>When we made the split of the teams we came up with 3 teams in the described setup. As we still are not where we want to be in terms of team size we always checked our approach to be scalable for more teams. Last month we just started a fourth team which integrated into our processes flawlessly.</p><p><em>4. Alignment needs to go beyond the development team</em></p><p>Alignment of priorities with other stakeholders is hard. Even though we came up with a clear roadmap (in most cases) and the idea that we can work on the issues one after another we got in trouble. Quite often priorities change. As the tech team is by definition running behind requirements you are facing the situation that the stakeholder is already working on topic B while the dev team has questions during implementation of topic A. Thats were inefficiency starts to pick up, especially with a capsulated dev team from the rest of the company. Now multiply this by 2 because stakeholders have the exact same issue. While working on topic B they need input from developers even though they are focused on implementing A.</p><p>With the continuos growth of the whole company, the number of teams you had to take into discussions grew as well making it complex and slow to have all the relevant people included.</p><p>The fact that we work with seasonal products where priorities change depending on the time of year makes it even worse.</p><p><em>5. The tradeoff between flexibility and focus</em></p><p>As described before, we decided against a focus for each development team for the benefit of diversification and flexibility when it comes to assigning issues. As there is no focus issue (customer, product, system) we experience some kind of a “lack of vision” for the teams which leads to lower passion for the sprint goal a team is working on and lower incentive to take responsibility and make educated decisions. Its impossible to develop a vision for your product/system/customer if you work on a new feature today for our configurator but you already know that in the next sprint you might be working on something completely different.</p><p>We managed to fix the problem of knowledge silos, though we might have overstepped the mark.</p><p>Overall we can say that we improved on the issues we wanted to tackle very well and made a lot of good progress on our output and outcome. Of course there is still a lot to do and we already have some ideas on how to tackle the next things. Stay tuned.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0af5476d802" width="1" height="1" alt=""><hr><p><a href="https://stories.celebrate.company/our-first-take-on-cross-functional-teams-b0af5476d802">Our first take on cross-functional teams</a> was originally published in <a href="https://stories.celebrate.company/">celebrate company</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>