<?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 Anneke Keller on Medium]]></title>
        <description><![CDATA[Stories by Anneke Keller on Medium]]></description>
        <link>https://medium.com/@anneke_72099?source=rss-f66783bb0d15------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*SccDoLt6eYjrM2akS6LX6Q.jpeg</url>
            <title>Stories by Anneke Keller on Medium</title>
            <link>https://medium.com/@anneke_72099?source=rss-f66783bb0d15------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 19:29:31 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@anneke_72099/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[Why Lego Technic™ is the microservices architecture of toys]]></title>
            <link>https://medium.com/jumbo-tech-campus/why-lego-technic-is-the-microservices-architecture-of-toys-e6b9ce07b5c5?source=rss-f66783bb0d15------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6b9ce07b5c5</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[outsourcing]]></category>
            <category><![CDATA[jumbo]]></category>
            <category><![CDATA[jumbo-tech-campus]]></category>
            <category><![CDATA[architecture]]></category>
            <dc:creator><![CDATA[Anneke Keller]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 07:45:40 GMT</pubDate>
            <atom:updated>2020-07-01T20:24:28.722Z</atom:updated>
            <content:encoded><![CDATA[<p>Like many bigger IT teams do, within the Jumbo Tech Campus we often talk about the development of our IT architecture. What parts do we want to develop ourselves, which parts would we like to develop in collaboration with our partners. And with whom do we want to do what. In my experience companies have a growth path when talking about technology, organisation and partnering. In the last 2 or 3 decades most companies have made steps in their development. Recognising those phases helps in defining where your IT currently is and what to do to improve it.</p><p>To illustrate the phases in which companies can be in their architecture and the relation with their partners, I made some pictures of toys of my daughter. They visualise the evolution of Lego, which , funny enough, nicely relate to the evolution of IT landscapes in many companies.</p><h4><em>Phase 1, DIY software</em></h4><p>Early in my career having a sourcing strategy for an IT team was simple. My team was part of the telecommunications company of the Netherlands, KPN. Because KPN had a monopoly on telephony, you could actually say we were “the” telecommunications company.</p><p>It was before 2000 and we were building the website and webshop for KPN, one of the first in the Netherlands. Many things were new and difficult, but one thing we didn’t need to spend a lot of time on was our build/buy decision. Should we buy a standard webshop and customise it to our own needs? Or should we build a platform ourselves?</p><p>The choice was quite simple, standard software for a webshop wasn’t available and therefore, we had to build it ourselves. Most companies did this, when they needed software, they had to specify the functionalities, make a functional and technical design and the software was specially built for that purpose. Often this was done in-house by a few developers in the technology they happened to know. This works fine as long as not too many processes within the company are automated; not too much functionality is required with enough money to invest in IT.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wpX6MyDxkqA6Wu67L0THVA.jpeg" /></figure><p>I promised to make a comparison with the toys. Historically toys were hand-made often from wood and every toy was made separately by a craftsman. With the advent of the industrial revolution, factories began to manufacture cheaper, standardized toys. The most famous example of this is probably the Lego factory in Denmark. This brings us to phase 2 in our journey, standardisation.</p><figure><img alt="Lego bricks" src="https://cdn-images-1.medium.com/max/1024/1*9HjI_X13uf-xuR99S2kXNA.jpeg" /></figure><h4><em>Phase 2, Standard products</em></h4><p>Before phase 2 every company had to build its own IT. Building software solutions from the ground up can be valid, but needless to say it is expensive and risky as well. Also as the technology wasn’t evolved as it is nowadays, it was quite difficult to code in general. On top of that the majority of processes were actually not specific to the company that had to develop them. This caused a big gap for companies. The market could definitely benefit from shared solutions that just covered the basics, so their developers could focus on the processes that made these companies unique.</p><p>One of the most straightforward examples is accounting software. Innovative software companies started filling this gap. The business case of such a company was very simple, they made a software product which was flexible enough to support several types of companies and sold those software products to these companies. This was beneficial for all players in the market: the suppliers could sell their product and for the customers their IT product became cheaper. Most code only had to be built once and could be used by different players.</p><p>At this moment in time for most companies buy/build decisions were still rather simple. If it was possible to buy the software you needed and if it wasn’t available you had to build it yourself.</p><h4><em>Phase 3, Customize, Customize, Customize</em></h4><figure><img alt="Branded Lego puppets" src="https://cdn-images-1.medium.com/max/1024/1*oXTG-FVHSO8YtXpsD7dr1A.jpeg" /></figure><p>So far, so good. The ability to leverage standard products gave a great boost both to the toys market and to the technology market. For toys it resulted in increased sales and a lot of happy children. But at a certain moment the growth couldn’t only come from replacing hand-made toys by more standard ones anymore. So the toys industry started to innovate. This was done in many ways, Lego chose to customise toys. Duplo for little children, special puppets who looked like movie stars, special Lego for girls etc. Again this was a great success and the market kept growing.</p><p>The software vendors were in a great position in this market, a lot of companies were dependent on them for (parts of) their software landscape and they were willing to pay for extra functionality. So software companies started to customise their software for the different clients, making a lot of money while doing that. This collaboration led to specific solutions that made it increasingly hard to switch vendor. This vendor lock was evidently beneficial for the vendor since it added to the longevity of their contracts. This, however, led to the next problem.</p><h4><em>Phase 4, Help! It is getting too complex</em></h4><p>All these highly customised solutions managed by our vendors slowly but surely became more troublesome than could be seen upfront.</p><figure><img alt="Lego mess" src="https://cdn-images-1.medium.com/max/1024/1*88iH7P8F97rMCM6hO7Z7-Q.jpeg" /></figure><p>This way-of-working slowly put us in trouble. Both the IT Suppliers as their customers had to deal with more and more complex landscapes. Despite the innovations the information technologies went through, development cycles started slowing down instead of speeding up. Code became increasingly unmaintainable and many customised landscapes became so complex that it became impossible to innovate any further on top of them.</p><p>We had to solve this problem from a technological perspective, and we started layering and decoupling our software. We added services and later microservices to disentangle big monolithic solutions. And finally, we divided our software to logically clustered business domains and still support the expected functionality, data handling etc. Even though this sounds like a pure technical difference, we actually had to restructure our organisational model to make this transition possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PnoM8k8j0-U9nQlRPhsyQg.jpeg" /></figure><p>Many technical challenges to make this transition can only be overcome when different technical disciplines work closely together. This was harder to do with a lot of outsourced work. So after years of outsourcing software, we started insourcing again. Good news for those among us who can code, since now every company wants you to work for them!</p><p>It’s hard to transition your organisational model when the majority of your proposition is outsourced. For the IT Suppliers, the urgency to move towards a microservices based architecture is low. Why would they invest in that? Going to a Service oriented architecture (SOA) has an initial complexity boundary to overcome, which many aren’t willing to take. Many vendors value rigidness over flexibility, because the vendor lock made them so much money earlier.</p><p>I believe many bigger (Dutch?) companies are nowadays in phase 4. Parts of our technological landscape are improving from an architectural perspective, but outsourced parts remain poor and hard to maintain.</p><h4><em>Phase 5, the future</em></h4><p>Finally, I believe, all enterprise software will convert to an architecture with isolation per business domain on a relatively fine granularity. I also believe this will take a while, like a lot of changes in IT take a while. Think about the mainframes that are outdated for many years and some of them are still running. Fortunately, you can do a lot to speed this process up by smartly organising your IT. Don’t wait for your suppliers to change their software, start building parts yourself. While doing that, try to implement best of breed, single purpose, well designed standard software wherever applicable. Preferably open-source, for which the developer base and longevity of the solution is bigger than for proprietary software. This means that you need less specific knowledge, easier recruiting, quicker security patches and longer community support. And I believe that this will bring you results in the short/mid-term. Well, at least it did for us within the Jumbo Tech Campus.</p><p>Going back to our Lego analogy, besides all the customising, Lego also innovated by developing Lego Technic. This also made it possible to make cooler toys that have more functionality than the original Lego bricks. But since Lego Technic is again based on small parts, that just could do more, it is very possible to make many toys with the same bricks. Making it the microservices solution of Lego.</p><figure><img alt="Lego Technic Hay Stack" src="https://cdn-images-1.medium.com/max/960/1*GeVSHF8cYcxJ0ma-pZuBvA.jpeg" /><figcaption><a href="https://mikeshouts.com/the-brick-wall-lego-technic-hay-rake/">https://mikeshouts.com/the-brick-wall-lego-technic-hay-rake/</a></figcaption></figure><p>Hope this story helps you with thinking about your own landscape, feel free to pay us a visit in Silicon Veghel :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6b9ce07b5c5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jumbo-tech-campus/why-lego-technic-is-the-microservices-architecture-of-toys-e6b9ce07b5c5">Why Lego Technic™ is the microservices architecture of toys</a> was originally published in <a href="https://medium.com/jumbo-tech-campus">Jumbo Tech Campus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cherry Picking]]></title>
            <link>https://medium.com/jumbo-tech-campus/cherry-picking-ea4eb311c7c9?source=rss-f66783bb0d15------2</link>
            <guid isPermaLink="false">https://medium.com/p/ea4eb311c7c9</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Anneke Keller]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 21:27:59 GMT</pubDate>
            <atom:updated>2018-12-06T21:29:07.378Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*4xAW_MlXlVmLw7NC4-fS0Q.png" /></figure><p>We are building the Jumbo Tech Campus since October last year. And since we wanted the Jumbo Tech Campus to be an organisation based on Agile principles, we re-organised ourselves recently. We implemented a new structure in our organisation that stimulates us to work in multi-disciplinary scrum teams and that allows us to scale.</p><p>Why? Well, Jumbo is a fast growing company that meanwhile transforms into a more technology focused company, so as an IT team, we need to be able to innovate and scale.</p><h4><strong>Our new structure</strong></h4><p>The organisational structure we implemented is pretty straight forward. We wanted to implement a best-practice, so that’s what we did. We started with the teams, these needed to be multi-disciplinary. Meaning that a team has all the skills to be able to implement a user story from A to Z. Depending on the task our teams have, they can consist of developers, testers, consultants, ops, designers etc. This makes sure that teams can implement stories from the start to the end.</p><p>The team has a product owner, who is in charge of the backlog and one of the team members of the team acts as a scrum master. We thrive to have all dedicated product owners and from experience we have learned that 1 product owner can support two teams. The teams also have a team lead, who is mainly focussed on coaching the team on both hard &amp; soft skills, hiring the right people and keeping an eye on the delivery of the team. So the team lead is the “HR manager”.</p><p>Two teams often have one team lead and one product owner. If you make a drawing it looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*uSO-WJQBWZGuQsFidtA6Og.png" /></figure><p>Indeed it looks like a cherry, which is a great metaphor for an agile team. Since a cherry has a strong pit, which stands for the hard skills a team needs to be effective. Team members need to be good at testing, developing or whatever their role is in the team. But a cherry also has a soft part, surrounding the whole pit. This stands for the soft skills a team needs to be effective. They need be a good team, working together not afraid to make mistakes and to get and give each other feedback.</p><p>Two teams with one lead we call a cell within our organisation and since we are a development team of around 300 people we have 35 teams all of them organised in the same way. There are around 15 team leads which are organised in three areas: Core, Digital and Data. These areas are managed by the development managers, so the team leads report into them.</p><h4>Learning</h4><p>One of the principles behind our development organisation is learning. We believe that when people can develop themselves, their job will be challenging, they will be more effective and more motivated to achieve great things together for Jumbo. Our organisation and our processes need to be set-up in such a way that it is easy for all members of the team to get feedback and learn. The scrum proces in itself is, of course, a good example of that, but also the team lead is very much focussed on coaching her/his team. Now we run into an issue, our teams are multi-disciplinary and it is the task of a team lead to coach the team also on hard-skills. Most of our team leads are from a development background and therefore coaching people in for example design, or testing is a challenge.</p><h4>Pathfinders</h4><p>Luckily we have one other team in our department, which is called our pathfinder team. Pathfinders are guru’s, really good at a specific skill. For example design, or agile and we have quite some technical pathfinders, focused on microservices, or infrastructure. Pathfinders have different tasks, one is to help team leads to coach on hard skills. Especially in the areas that team leads aren’t very much skilled in. So our Design pathfinder helps many leads to recruit the right people for their teams.</p><p>The name pathfinders isn’t accidentally chosen, they do “find the right path”. Especially between the different teams. We like the teams to be very autonomous, making a lot of decisions themselves. But teams do not always know the answers themselves and they like to get help. Also there are topics that should be aligned for the whole department. Things like code guidelines, design guidelines etc. These are all typical pathfinder topics.</p><p>We always say that making mistakes isn’t a problem. As long as you learn from them and do better next time. On the other hand, we have 35 teams. And although making mistakes is part of the learning proces, we do not have to make the same mistake 35 times. Pathfinders avoid this.</p><h4>How do we innovate?</h4><p>We’ve implemented this structure to be able to innovate faster. How does this work. Well, scrum is a process in which you try to make all improvements small and fast. Making sure that you can develop new stuff quickly, implement it quickly and learn what your users/customers think of it. Which this feedback you can improve your software until it is good enough. Within our E-commerce environment we are pretty far in this sense. We can already release more times per day.</p><h4>How does this organisation scale?</h4><p>The organisation is pretty straight forward and scales by adding more cells to the structure. More cherries in the tree so to speak. This means we’ll have more teams, more team leads and maybe an extra development manager is needed at a certain point.</p><h4><strong>Best practice</strong></h4><p>In general, I believe Jumbo should, when talking about IT, have a best-practices strategy. In the end we are in the business of selling groceries the best way possible and not in the business of inventing new (software development) processes. So the whole story above is not unique for an IT team. It is mainly a best-practise within the IT world on how software should be build and how an IT team should be organised.</p><h4><strong>Cherry-model</strong></h4><p>As said, we are in this new organisation now for a few months. So now we start noticing how things work out. This is the moment that your team members start asking questions. Very relevant questions most of the time. And there is one question that is asked many times, especially by people that have seen other agile implementations in other companies:</p><blockquote>Why is a scrum master not a dedicated function in itself, but a role of someone in the team? And why is there a separate team lead who is HR responsible?</blockquote><p>I heard people talking about the “cherry-model” of Jumbo. In the beginning I didn’t understand why people talked about it. We implemented a best-practice, so what was special about the Jumbo version?</p><p>But later I realised, when designing our organisation we followed the scrum principles very thoroughly, “scrum-by-the-book”. Maybe a bit more than most companies do. So we indeed might have done something a little bit different than the mainstream. And I believe this was a very wise choice, let me explain why.</p><p>The essence of scrum is not implementing the process we all know, the rituals. It is about building a culture and building cultures isn’t easy. To make that happen in a big development team you need to do a lot. Actually everything that can help, you should do. And that’s the reason why I strongly believe the cherry model works. One thing to add here is that I do not believe in completely autonomous teams. I do believe in fairly autonomous teams; especially in larger IT teams I believe that some kind of <em>normal</em> HR is needed and actually very much appreciated by the people that work there. One of the reasons is that work motivation is very often strongly related to the speed in which you can learn. Learning fast is very often facilitated by some kind of mentor or coach and that is very often your manager or lead.</p><p>To build a scrum culture you need to do everything you can to make it easy for people to talk about their mistakes</p><p>With the cherry model you split the responsibility of HR from the responsibility to make the scrum proces work. Meaning the team can do its proces as autonomous as possible, without a manager kind of type interfering. So when you are in a retro, the lead doesn’t need to be there making it safer to talk about your failures.</p><p>Also sometimes teams get in trouble, they can’t solve it themselves anymore. A lead is than an outsider, objective to whatever matter is at hand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ea4eb311c7c9" width="1" height="1" alt=""><hr><p><a href="https://medium.com/jumbo-tech-campus/cherry-picking-ea4eb311c7c9">Cherry Picking</a> was originally published in <a href="https://medium.com/jumbo-tech-campus">Jumbo Tech Campus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cherry Picking]]></title>
            <link>https://medium.com/@anneke_72099/cherry-picking-200206b60289?source=rss-f66783bb0d15------2</link>
            <guid isPermaLink="false">https://medium.com/p/200206b60289</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Anneke Keller]]></dc:creator>
            <pubDate>Mon, 03 Dec 2018 20:27:28 GMT</pubDate>
            <atom:updated>2018-12-03T21:26:40.658Z</atom:updated>
            <content:encoded><![CDATA[<p>We are building the Jumbo Tech Campus since October last year. And since we wanted the Jumbo Tech Campus to be an organisation based on Agile principles, we re-organised ourselves recently. We implemented a new structure in our organisation that stimulates us to work in multi-disciplinary scrum teams and that allows us to scale.</p><p>Why? Well, Jumbo is a fast growing company that meanwhile transforms into a more technology focused company, so as an IT team, we need to be able to innovate and scale.</p><h4><strong>Our new structure?</strong></h4><p>The organisational structure we implemented is pretty straight forward. We wanted to implement a best-practice, so that’s what we did. We started with the teams, these needed to be multi-disciplinary. Meaning that a team has all the skills to be able to implement a user story from A to Z. Depending on the task our teams have, they can consist of developers, testers, consultants, ops, designers etc. This makes sure that teams can implement stories from the start to the end.</p><p>The team has a product owner, who is in charge of the backlog and one of the team members of the team acts as a scrum master. We thrive to have all dedicated product owners and from experience we have learned that 1 product owner can support two teams. The teams also have a team lead, who is mainly focussed on coaching the team on both hard &amp; soft skills, hiring the right people and keeping an eye on the delivery of the team. So the team lead is the “HR manager”.</p><p>Two teams often have one team lead and one product owner. If you make a drawing it looks like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/589/1*AjfrcbvQvd0iAN_VLxr6JA.png" /></figure><p>Indeed it looks like a cherry, which is a great metaphor for an agile team. Since a cherry has a strong pit, which stands for the hard skills a team needs to be effective. Team members need to be good at testing, developing or whatever their role is in the team. But a cherry also has a soft part, surrounding the whole pit. This stands for the soft skills a team needs to be effective. They need be a good team, working together not afraid to make mistakes and to get and give each other feedback.</p><p>Two teams with one lead we call a cell within our organisation and since we are a development team of around 300 people we have 35 teams all of them organised in the same way. There are around 15 team leads which are organised in three areas: Core, Digital and Data. These areas are managed by the development managers, so the team leads report into them.</p><p>One of the principles behind our development organisation is learning. We believe that when people can develop themselves, their job will be challenging, they will be more effective and more motivated to achieve great things together for Jumbo. Our organisation and our processes need to be set-up in such a way that it is easy for all members of the team to get feedback and learn. The scrum proces in itself is, of course, a good example of that, but also the team lead is very much focussed on coaching her/his team. Now we run into an issue, our teams are multi-disciplinary and it is the task of a team lead to coach the team also on hard-skills. Most of our team leads are from a development background and therefore coaching people in for example design, or testing is a challenge.</p><p>Luckily we have one other team in our department, which is called our pathfinder team. Pathfinders are guru’s, really good at a specific skill. For example design, or agile and we have quite some technical pathfinders, focused on microservices, or infrastructure. Pathfinders have different tasks, one is to help team leads to coach on hard skills. Especially in the areas that team leads aren’t very much skilled in. So our Design pathfinder helps many leads to recruit the right people for their teams.</p><p>The name pathfinders isn’t accidentally chosen, they do “find the right path”. Especially between the different teams. We like the teams to be very autonomous, making a lot of decisions themselves. But teams do not always know the answers themselves and they like to get help. Also there are topics that should be aligned for the whole department. Things like code guidelines, design guidelines etc. These are all typical pathfinder topics.</p><p>We always say that making mistakes isn’t a problem. As long as you learn from them and do better next time. On the other hand, we have 35 teams. And although making mistakes is part of the learning proces, we do not have to make the same mistake 35 times. Pathfinders avoid this.</p><h4><strong>How do we innovate?</strong></h4><p>We’ve implemented this structure to be able to innovate faster. How does this work. Well, scrum is a process in which you try to make all improvements small and fast. Making sure that you can develop new stuff quickly, implement it quickly and learn what your users/customers think of it. Which this feedback you can improve your software until it is good enough. Within our E-commerce environment we are pretty far in this sense. We can already release more times per day.</p><h4>How does this organisation scale?</h4><p>The organisation is pretty straight forward and scales by adding more cells to the structure. More cherries in the tree so to speak. This means we’ll have more teams, more team leads and maybe an extra development manager is needed at a certain point.</p><h4><strong>Best practice</strong></h4><p>In general, I believe Jumbo should, when talking about IT, have a best-practices strategy. In the end we are in the business of selling groceries the best way possible and not in the business of inventing new (software development) processes. So the whole story above is not unique for an IT team. It is mainly a best-practise within the IT world on how software should be build and how an IT team should be organised.</p><h4><strong>Cherry-model</strong></h4><p>As said, we are in this new organisation now for a few months. So now we start noticing how things work out. This is the moment that your team members start asking questions. Very relevant questions most of the time. And there is one question that is asked many times, especially by people that have seen other agile implementations in other companies:</p><blockquote>Why is a scrum master not a dedicated function in itself, but a role of someone in the team? And why is there a separate team lead who is HR responsible?</blockquote><p>I heard people talking about the “cherry-model” of Jumbo. In the beginning I didn’t understand why people talked about it. We implemented a best-practice, so what was special about the Jumbo version?</p><p>But later I realised, when designing our organisation we followed the scrum principles very thoroughly, “scrum-by-the-book”. Maybe a bit more than most companies do. So we indeed might have done something a little bit different than the mainstream. And I believe this was a very wise choice, let me explain why.</p><p>The essence of scrum is not implementing the process we all know, the rituals. It is about building a culture and building cultures isn’t easy. To make that happen in a big development team you need to do a lot. Actually everything that can help, you should do. And that’s the reason why I strongly believe the cherry model works. One thing to add here is that I do not believe in completely autonomous teams. I do believe in fairly autonomous teams; especially in larger IT teams I believe that some kind of <em>normal</em> HR is needed and actually very much appreciated by the people that work there. One of the reasons is that work motivation is very often strongly related to the speed in which you can learn. Learning fast is very often facilitated by some kind of mentor or coach and that is very often your manager or lead.</p><p>To build a scrum culture you need to do everything you can to make it easy for people to talk about their mistakes</p><p>With the cherry model you split the responsibility of HR from the responsibility to make the scrum proces work. Meaning the team can do its proces as autonomous as possible, without a manager kind of type interfering. So when you are in a retro, the lead doesn’t need to be there making it safer to talk about your failures.</p><p>Also sometimes teams get in trouble, they can’t solve it themselves anymore. A lead is than an outsider, objective to whatever matter is at hand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=200206b60289" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>