<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Teamwork on Humbly Proud</title>
    <link>https://humblyproud.com/en/tags/teamwork/</link>
    <description>Recent content in Teamwork on Humbly Proud</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <copyright>Toni Tassani. All rights reserved.</copyright>
    <atom:link href="https://humblyproud.com/en/tags/teamwork/rss.xml" rel="self" type="application/rss&#43;xml" /><item>
      <title>Starting with a team</title>
      <link>https://humblyproud.com/en/blog/starting-with-a-team/</link>
      <pubDate>Fri, 20 Nov 2026 00:00:00 &#43;0000</pubDate>
      <lastBuildDate>Fri, 20 Nov 2026 00:00:00 &#43;0000</lastBuildDate>
      <guid>https://humblyproud.com/en/blog/starting-with-a-team/</guid>
      <description><![CDATA[<img src="https://humblyproud.com/en/blog/starting-with-a-team/images/18-startingteam-rocket.jpg" alt="Featured image of post Starting with a team" /><p>It is common to believe that a team, to perform well, must be stable, properly sized, working face-to-face, with an appointed leader, and a clear task. The leader gets a collection of individuals and helps them perform together, achieving as a group much more than they could do individually. On this basis, what is the magic that the leader does? Is the appointed leader the one in charge of that?</p>
<h2 id="effective-teams">Effective teams
</h2><p>Richard Hackman was a professor of Social and Organisational Psychology at Harvard University, studying teams and their performance. In his book <a class="link" href="https://www.goodreads.com/en/book/show/11600687-collaborative-intelligence"  target="_blank" rel="noopener"
    ><em>Collaborative intelligence</em></a>, the conditions that make a team more likely to be successful are the following <a class="link" href="#ref-hackmanCollaborativeIntelligenceUsing2011" >[1, Pt.II]</a>:</p>
<ol>
<li>Having a real team<br>
<em>With known boundaries and interdependence.</em></li>
<li>A compelling purpose<br>
<em>Clear, challenging, consequential and incomplete.</em></li>
<li>The right number of the right people<br>
<em>As small and diverse as possible.</em></li>
<li>Clear norms of conduct<br>
<em>It will reduce the amount of time spent managing behaviour.</em></li>
<li>Supportive organisational context<br>
<em>Having the material resources and an information system.</em></li>
<li>Team-focused coaching available<br>
<em>With a different focus at different stages.</em></li>
</ol>
<figure>
<img src="images/18-startingteam-rocket.jpg" height="300" alt="Starting a team" />
<figcaption aria-hidden="true">Starting a team</figcaption>
</figure>
<p>Hackman says that how well a team performs depends on what he calls the 60-30-10 rule (not a scientific rule, but a rule of thumb) <a class="link" href="#ref-hackmanCollaborativeIntelligenceUsing2011" >[1, Ch. 10]</a>. Sixty per cent depends on the quality of the pre-work the team leader does. Thirty per cent on the initial launch of the team. And only ten per cent depends on what the team leader does after the team is underway with their work.</p>
<p>Most of the items Hackman suggests can be achieved by the leader before the team members arrive, and the rest have to be done early in the life of the team, like setting <em>clear norms of conduct</em>. Edgar Schein, in <a class="link" href="https://www.goodreads.com/book/show/222096.Organizational_Culture_and_Leadership"  target="_blank" rel="noopener"
    ><em>Organisational culture and leadership</em></a>, uses Bruce Tuckman’s model to describe the stages of a team: <em>forming</em>, <em>storming</em>, <em>norming</em>, and <em>performing</em> <a class="link" href="#ref-scheinOrganizationalCultureLeadership2017" >[2, Ch. 8]</a>. The performance of the team can be limited if tasks are given far before the <em>norming</em> stage, he says.</p>
<h2 id="launch-a-team">Launch a team
</h2><p>The book <a class="link" href="https://www.goodreads.com/book/show/13493815-liftoff"  target="_blank" rel="noopener"
    ><em>Liftoff</em></a> suggests a collection of activities to perform when starting with a team <a class="link" href="#ref-larsenLiftoffLaunchingAgile2012" >[3]</a>. They call them Agile Chartering because they focus on teams practising agile methods. The activities are both <em>task oriented</em> and <em>relationships oriented</em>. They consider three elements: <em>purpose</em>, <em>alignment</em>, and <em>context</em>.</p>
<p>For the <em>purpose</em>, the team sets the direction and the motivation including the <em>product vision</em> and the <em>team mission</em>. For the <em>alignment</em>, they create <em>simple rules</em>, form the <em>core team</em> and create <em>working agreements</em>. And for the <em>context</em>, they define <em>team boundaries</em> and clarify <em>resources committed</em>.</p>
<p>The main ideas of the Liftoff are executed in a workshop with the whole team, but there are many things that can be done by the team leader even before the team is hired.</p>
<h2 id="the-preparation">The preparation
</h2><p>There are many activities to explore and clarify before the team arrives. The following list can give the team leader some ideas:</p>
<ul>
<li>Study the context. The department, stakeholders, dependencies, budget, expectations, required skills, existing solutions.</li>
<li>Build relationships and set expectations. Get to know management, peers, and stakeholders.</li>
<li>Identify the team’s mission and purpose. Maybe it is already defined. The cascading goals or OKRs will be important.</li>
<li>Business KPIs. How to measure success and what is important.</li>
<li>Review team composition. Existing team members, vacancies, and recruitment status.</li>
</ul>
<h3 id="some-ideas-from-ocado-technology-colleagues-on-the-preparation">Some ideas from Ocado Technology colleagues on the preparation
</h3><p>For the preparation part, Colin Rouse, Engineering Manager in Supply Chain and Planning (LSCN), gets inspiration from the book <a class="link" href="https://www.goodreads.com/book/show/16158601-turn-the-ship-around"  target="_blank" rel="noopener"
    ><em>Turn the ship around</em></a>. Apart from the idea of “thinking out loud”, he asks management, stakeholders and team members the following questions from the book to understand expectations <a class="link" href="#ref-marquetTurnShipTrue2015" >[4, p. 24]</a>:</p>
<ol>
<li>What are the things you are hoping I don’t change?</li>
<li>What are the things you secretly hope I do change?</li>
<li>What are the good things about X we should build on?</li>
<li>If you were me, what would you do first?</li>
<li>Why isn’t X doing better?</li>
<li>What are your personal goals for your participation in X?</li>
<li>What impediments do you have to do your job?</li>
<li>What will be our biggest challenge to getting X ready for go-live?</li>
<li>What are your biggest frustrations about how X is currently organised / run?</li>
<li>What is the best thing I can do for you?</li>
</ol>
<p>Patryk Kosek, Engineering Manager in OSP Now - WMS (LSCN), also uses books as his source of inspiration for starting with a team. <a class="link" href="https://www.goodreads.com/book/show/763362.The_One_Minute_Manager"  target="_blank" rel="noopener"
    ><em>The one minute manager</em></a> by Ken Blanchard is about situational leadership (<em>directing</em>, <em>coaching</em>, <em>supporting</em> and <em>delegating</em>), and helps him in understanding how mature a team is and how to facilitate meetings efficiently. <a class="link" href="https://www.goodreads.com/book/show/36072.The_7_Habits_of_Highly_Effective_People"  target="_blank" rel="noopener"
    ><em>The 7 habits of highly effective people</em></a> has many insights for him. The “seek first to understand” habit inspires him to get to know all the stakeholders and team members — who they are and what they need —, and to understand boundaries and dependencies. “Begin with the end in mind” helps him to think about the mission and ways of working. “Sharpen the saw” guides him to think about improvement. He also recommends the audiobook version of <a class="link" href="https://www.goodreads.com/book/show/81107.The_Energy_Bus"  target="_blank" rel="noopener"
    ><em>The energy bus</em></a> by Jon Gordon, about attitude, focus, and vision.</p>
<h2 id="the-launch">The launch
</h2><p>The workshop suggested in Liftoff is a practice known with many other names, usually related to projects more than teams: kickstart, kick-off, launch, or boot camp.</p>
<p>It is important that the whole team participates and it can be a single session or many sessions distributed on different days.</p>
<p>In order to be effective, the event has to be carefully prepared. There will be a good balance of <em>task-oriented</em> activities and <em>relationship-oriented</em> activities. These are some things to prepare before getting together:</p>
<ul>
<li>Create the agenda.</li>
<li>Clarify primary and secondary goals for the workshop.</li>
<li>Set up the sessions: invites, book rooms, arrange travel if needed, catering, etc.</li>
<li>Research for the <em>task-oriented</em> activities: constraints, dependencies, existing processes, etc.</li>
<li>Research for the <em>relationship-oriented</em> activities, for instance, run an Insights assessment.</li>
</ul>
<p>This pre-work can be done with team members, product, or business people and, if possible, with the help of a facilitator.</p>
<blockquote>
<p><em>Team leader</em> is singular, whereas team <em>leadership</em> can be, and usually should be, plural.<br>
— Richard Hackman (Collaborative Intelligence)</p>
</blockquote>
<p>One of the most important activities to be run with all the team is the definition of the “ways of working”, “team rules”, “norms of conduct”, or “operating guidelines”, you name them. These norms will be a living document but they need to be explicit. In <a class="link" href="https://www.goodreads.com/book/show/1500441.Leading_Teams"  target="_blank" rel="noopener"
    ><em>Leading teams</em></a>, Hackman suggests that some norms can be “imported” from previous team member’s experiences <a class="link" href="#ref-hackmanLeadingTeamsSetting2002" >[5, Ch. 4]</a>. In episode 192 of the podcast <em>Coaching for leaders</em> they presented some ideas for <a class="link" href="https://coachingforleaders.com/podcast/192/"  target="_blank" rel="noopener"
    >creating team guidelines</a> <a class="link" href="#ref-stachowiak192HowCreate2015" >[6]</a>.</p>
<p>For the <em>task-oriented</em> activities, you can find inspiration in the book <a class="link" href="https://www.goodreads.com/book/show/23162381-kanban-from-the-inside"  target="_blank" rel="noopener"
    ><em>Kanban from the inside</em></a> <a class="link" href="#ref-burrowsKanbanUnderstandKanban2014" >[7, Ch. 23]</a> and in <a class="link" href="https://simplifychange.se/wp-content/uploads/2016/10/Kanban-Kick-start-Field-Guide-v1.1.pdf"  target="_blank" rel="noopener"
    ><em>The Kanban kick-start field guide</em></a> <a class="link" href="#ref-achouiantzKanbanKickstartField2013" >[8]</a>. These are some of the activities you could consider discussing during the session:</p>
<ul>
<li>Share current concerns (sources of dissatisfaction).</li>
<li>Define a shared purpose.</li>
<li>Create a name for the team (and a logo).</li>
<li>Discover what the team does today.</li>
<li>Understand where work comes from and how.</li>
<li>Identify work types, granularity and service level expectations.</li>
<li>Set visualisation policies (and consider blockers and dependencies).</li>
<li>Agree on transition criteria (Definition of Done and Definition of Ready).</li>
<li>Create and populate the board.</li>
<li>Set “ways of working”.</li>
<li>Define the meetings: who is involved and at what cadences.</li>
<li>Agree on how to communicate within the team (internal) and with other stakeholders (external).</li>
</ul>
<h3 id="some-ideas-from-our-colleagues-on-the-launch">Some ideas from our colleagues on the launch
</h3><p>Marco Delgado, Engineering Practice Lead in Engineering Practices (EngProd), when he was a Team Leader starting the Krakens team in 2019, used three sessions of one hour and a half each, spaced within two weeks for their launch event. They could enjoy having Nathan Leftwich as a facilitator, which allowed Marco to be a participant. The three sessions had the following topics:</p>
<ol>
<li>Remit, focus and purpose.</li>
<li>Our team and who we are. Team background and foundation, using <a class="link" href="https://www.16personalities.com/"  target="_blank" rel="noopener"
    >16 personalities</a> (another <a class="link" href="/en/blog/2022-06-30-useful-nonsense/" >psychometric</a> test) to fuel discussion and create the team name.</li>
<li>Ways of working, identify stakeholders, define how to track work and how to work together.</li>
</ol>
<p>Colin Rouse likes to explain the ideas from the book <a class="link" href="https://www.goodreads.com/book/show/21343.The_Five_Dysfunctions_of_a_Team"  target="_blank" rel="noopener"
    ><em>The five dysfunctions of a team</em></a> because it explains why he starts focusing on relationships <a class="link" href="#ref-lencioniFiveDysfunctionsTeam2013" >[9]</a>. He also finds <a class="link" href="https://engineering.atspotify.com/2014/09/16/squad-health-check-model/"  target="_blank" rel="noopener"
    >squad health checks</a> useful <a class="link" href="#ref-knibergSquadHealthCheck2014" >[10]</a>. He likes to set clear roles and responsibilities and set expectations using <a class="link" href="https://management30.com/practice/delegation-poker/"  target="_blank" rel="noopener"
    >delegation poker</a> <a class="link" href="#ref-appeloManagingHappinessGames2016" >[11, Ch. 3]</a> and a <a class="link" href="https://management30.com/practice/competency-matrix/"  target="_blank" rel="noopener"
    >competency matrix</a>.</p>
<p>Adam Barke, Engineering Team Leader in Klaxons (LSCN), considers that the fundamental elements of starting with a team have to include establishing “How we work” and ensuring the team knows the mission and goals. Motivation and clear expectations are key to him. Teams can also gain a sense of identity through coming up with a team name which can also act as an early team building exercise instilling a sense of fun into their work.</p>
<p>Anna Pszczółkowska, Engineering Team Leader in Fremen (EngProd), likes to be explicit about expectations from each member to the different roles: ETL, PM and UX. She uses the <a class="link" href="https://www.funretrospectives.com/role-expectations-matrix/"  target="_blank" rel="noopener"
    >role expectations matrix</a> and the <a class="link" href="https://management30.com/practice/delegation-poker/"  target="_blank" rel="noopener"
    >delegation poker</a> techniques.</p>
<p>Alberto Rodríguez, Engineering Manager in Customer (Ecommerce), finds the <a class="link" href="https://management30.com/practice/personal-maps/"  target="_blank" rel="noopener"
    >personal maps</a> exercise useful to get to know the team <a class="link" href="#ref-appeloManagingHappinessGames2016" >[11, p. 39]</a>. He also recommends adding a periodic event in the calendar to revisit the “ways of working”.</p>
<h2 id="the-follow-up">The follow-up
</h2><p>Once the team is set up and working, some adjustments will have to occur. The team has to ensure they are working on the right thing and in the right way, assuming that there are always options to do it better. Fine-tuning, with the participation of the whole team, how we plan work, how we address incidents or how we communicate priorities, for instance. A usual technique to address improvements is the <em>retrospective</em>, but there are many others.</p>
<h3 id="some-ideas-from-our-colleagues-on-the-follow-up">Some ideas from our colleagues on the follow-up
</h3><p>For Xavi Rodríguez, Engineering Manager in Observability (EngProd), when he was a team leader working on the Payments handover from Hatfield to Barcelona, learning and knowledge sharing was essential. They used a “virtual room,” a shared Google Slides document describing how they worked as a team —practices, workflow, and routines, — that was constantly reviewed and updated by all team members. They also scheduled a weekly one-hour meeting for knowledge sharing and created mechanisms to detect blind spots and silos.</p>
<p>For knowledge sharing, Alberto Rodríguez has used <a class="link" href="http://leancoffee.org/"  target="_blank" rel="noopener"
    >Lean Coffee</a>, but he also sees that sometimes is not enough.</p>
<p>Marco Delgado’s Krakens, when they were already performing, decided to adopt weekly plannings and retrospectives. They also invented the rotating role of “The King of the board”, taking on the role of a product manager, making sure the board was updated and the work properly sized.</p>
<p>Colin Rouse finds it useful to run activities so team members feel part of the company. The buddy route, visiting CFCs or doing some meet-and-greet with other teams. When the teams are trying to improve, Colin prefers to focus on just one thing and improve to deliver better.</p>
<p>Anna Pszczółkowska has experimented during the pandemic with a permanent Google Meet, weekly retrospectives and playing <a class="link" href="https://www.haxball.com/"  target="_blank" rel="noopener"
    >haxball</a> for 10 minutes before the daily. They also use other activities to build relationships, sometimes run during the retro: <a class="link" href="https://www.sessionlab.com/methods/coat-of-arms"  target="_blank" rel="noopener"
    >coat of arms</a>, <a class="link" href="https://www.funretrospectives.com/draw-your-feelings/"  target="_blank" rel="noopener"
    >draw your feelings</a> and “Getting to know each other” questions in the Ocado 1-2-1 cards.</p>
<h2 id="a-taste-of-reality">A taste of reality
</h2><p>The team leader does not always arrive before the team. The team does not find a blank slate. Team members come and go and the mission can be changed. Teams do not stay at the Tuckman’s <em>perform</em> stage and live there happily ever after. Life happens.</p>
<p>Sometimes it feels right to re-start and get the benefits of the team launch. Hackman says that a team can be re-launched effectively <a class="link" href="#ref-hackmanCollaborativeIntelligenceUsing2011" >[1, Ch. 9]</a>.</p>
<p>Stability in teams is relative. New team members may arrive or leave for new challenges. The mission may change and there can be promotions or retirements. Heidi Helfand in <a class="link" href="https://www.goodreads.com/book/show/32853178-dynamic-reteaming"  target="_blank" rel="noopener"
    ><em>Dynamic Reteaming</em></a> discusses what can be done in what she calls “team calibration sessions” <a class="link" href="#ref-helfandDynamicReteamingArt2020" >[12, Ch. 13]</a>.</p>
<h3 id="addressing-reality-the-ocado-way">Addressing reality, the Ocado Way
</h3><p>Teams evolve and during the COVID pandemic many things taken for granted, like face to face communication, had to adapt.</p>
<p>Ed Marwood, Engineering Team Leader in Problem Management (EngProd), recruited two new people during the pandemic and never met them in person. He found the <em>technical onboarding</em> provided by The Academy helpful and all the resources from People. He enjoyed being able to reach out to other Engineering Team Leaders and Ocado’s support community. They created a lot of structure for the new joiners, like an <em>assessment</em> to score themselves on skills, and an <em>onboarding checklist</em>. Some existing team members acted as <em>mentors</em> for the new members, explaining the day to day work.</p>
<p>Colin Rouse also likes the figure of <em>buddies</em> or <em>mentors</em>, because we can easily underestimate how hard it is to land. The most recently on-boarded members know better how to make the newcomers feel safe.</p>
<p>Anna Pszczółkowska also uses a checklist for induction but they use a Miro board to track it and they like it to be a process guided by the new-joiners at their own pace.</p>
<p>Alberto Rodríguez could not have the whole team when starting Typos and had to balance between “what they should do” and “what they could do”. Sometimes you have to postpone the “ways of working” and sometimes you don’t have enough information to discuss the mission and the vision.</p>
<p>Julia Łucka, Engineering Team Leader in CFC Outbound - Picking - Config. &amp; Deployment (Fulfilment), had a lot of changes during the pandemic, including new team members and a change of mission. The team decided to have one meeting per day with the new joiner for two weeks, each session with a different team member on a specific topic. It was paced, reducing anxiety. They covered topics like “how to do CI”, “how to do back-end”, or “the technical setup”. They created a <em>checklist of things to experience in the first month</em>, like “accessing logs”, “deploying to production”, or “participating in a backlog grooming”. And they reviewed the checklist in one-to-ones. To ease the on-boarding experience whilst remote they included social events every two weeks for two months during working hours, with activities like quizzes and sharing childhood photos. They also discussed <a class="link" href="https://www.belbin.com/about/belbin-team-roles"  target="_blank" rel="noopener"
    >Belbin roles</a> as a tool to improve relationships.</p>
<p>There are many good ideas for starting with a team. How can we share them?</p>
<p>Toni Tassani — 20 Nov 2026</p>
<p>This article was originally published on 31 May 2021 on the Ocado Technology intranet.</p>
<hr>
<div id="refs" class="references csl-bib-body" data-entry-spacing="0">
<div id="ref-hackmanCollaborativeIntelligenceUsing2011" class="csl-entry">
<p><span class="csl-left-margin">[1] </span><span class="csl-right-inline">J. Richard Hackman, <em>Collaborative Intelligence: Using Teams to Solve Hard Problems</em>. San Francisco, CA: Berrett-Koehler Publishers, 2011 [Online]. Available: <a class="link" href="https://learning.oreilly.com/library/view/collaborative-intelligence/9781605099910/"  target="_blank" rel="noopener"
    >https://learning.oreilly.com/library/view/collaborative-intelligence/9781605099910/</a>. [Accessed: 11-Jan-2021]</span></p>
</div>
<div id="ref-scheinOrganizationalCultureLeadership2017" class="csl-entry">
<p><span class="csl-left-margin">[2] </span><span class="csl-right-inline">Edgar H. Schein and Peter Schein, <em>Organizational Culture and Leadership</em>, 5th edition. Hoboken, New Jersey: Wiley, 2017 [Online]. Available: <a class="link" href="https://learning.oreilly.com/library/view/organizational-culture-and/9781119212041/"  target="_blank" rel="noopener"
    >https://learning.oreilly.com/library/view/organizational-culture-and/9781119212041/</a></span></p>
</div>
<div id="ref-larsenLiftoffLaunchingAgile2012" class="csl-entry">
<p><span class="csl-left-margin">[3] </span><span class="csl-right-inline">Diana Larsen and Ainsley Nies, <em>Liftoff: Launching Agile Teams &amp; Projects</em>. Hillsboro, OR: Onyx Neon, 2012 [Online]. Available: <a class="link" href="https://learning.oreilly.com/library/view/liftoff-2nd-edition/9781680501971/"  target="_blank" rel="noopener"
    >https://learning.oreilly.com/library/view/liftoff-2nd-edition/9781680501971/</a></span></p>
</div>
<div id="ref-marquetTurnShipTrue2015" class="csl-entry">
<p><span class="csl-left-margin">[4] </span><span class="csl-right-inline">L. David Marquet, <em>Turn the Ship around! A True Story of Turning Followers into Leaders</em>. New York: Portfolio Penguin, 2015.</span></p>
</div>
<div id="ref-hackmanLeadingTeamsSetting2002" class="csl-entry">
<p><span class="csl-left-margin">[5] </span><span class="csl-right-inline">J. Richard Hackman, <em>Leading Teams: Setting the Stage for Great Performances</em>. Boston, Mass: Harvard Business School Press, 2002 [Online]. Available: <a class="link" href="https://learning.oreilly.com/library/view/leading-teams/9781633691216/"  target="_blank" rel="noopener"
    >https://learning.oreilly.com/library/view/leading-teams/9781633691216/</a></span></p>
</div>
<div id="ref-stachowiak192HowCreate2015" class="csl-entry">
<p><span class="csl-left-margin">[6] </span><span class="csl-right-inline">Dave Stachowiak and Susan Gerke, “192: How to Create Team Guidelines, with Susan Gerke,” [Audio podcast], <em>Coaching for Leaders</em>, 11-May-2015. [Online]. Available: <a class="link" href="https://coachingforleaders.com/podcast/192/"  target="_blank" rel="noopener"
    >https://coachingforleaders.com/podcast/192/</a>. [Accessed: 21-May-2021]</span></p>
</div>
<div id="ref-burrowsKanbanUnderstandKanban2014" class="csl-entry">
<p><span class="csl-left-margin">[7] </span><span class="csl-right-inline">Mike Burrows, <em>Kanban from the inside: Understand the Kanban Method, Connect It to What You Already Know, Introduce It with Impact</em>. Seqium, Washington: Blue Hole Press, 2014.</span></p>
</div>
<div id="ref-achouiantzKanbanKickstartField2013" class="csl-entry">
<p><span class="csl-left-margin">[8] </span><span class="csl-right-inline">Christophe Achouiantz and Johan Nordin, “The Kanban Kick-start Field Guide: Create the Capability to Evolve.” 25-Nov-2013 [Online]. Available: <a class="link" href="https://simplifychange.se/wp-content/uploads/2016/10/Kanban-Kick-start-Field-Guide-v1.1.pdf"  target="_blank" rel="noopener"
    >https://simplifychange.se/wp-content/uploads/2016/10/Kanban-Kick-start-Field-Guide-v1.1.pdf</a></span></p>
</div>
<div id="ref-lencioniFiveDysfunctionsTeam2013" class="csl-entry">
<p><span class="csl-left-margin">[9] </span><span class="csl-right-inline">Patrick M. Lencioni, <em>The Five Dysfunctions of a Team: A Leadership Fable</em>. San Francisco, Calif.: Jossey-Bass, 2013 [Online]. Available: <a class="link" href="https://learning.oreilly.com/library/view/the-five-dysfunctions/9780787960759/"  target="_blank" rel="noopener"
    >https://learning.oreilly.com/library/view/the-five-dysfunctions/9780787960759/</a>. [Accessed: 04-Dec-2020]</span></p>
</div>
<div id="ref-knibergSquadHealthCheck2014" class="csl-entry">
<p><span class="csl-left-margin">[10] </span><span class="csl-right-inline">Henrik Kniberg and Kristian Lindwall, “Squad Health Check model - visualizing what to improve,” <em>Spotify Engineering</em>, 16-Sept-2014. [Online]. Available: <a class="link" href="https://engineering.atspotify.com/2014/09/16/squad-health-check-model/"  target="_blank" rel="noopener"
    >https://engineering.atspotify.com/2014/09/16/squad-health-check-model/</a>. [Accessed: 22-May-2021]</span></p>
</div>
<div id="ref-appeloManagingHappinessGames2016" class="csl-entry">
<p><span class="csl-left-margin">[11] </span><span class="csl-right-inline">Jurgen Appelo, <em>Managing for Happiness: Games, Tools, and Practices to Motivate Any Team</em>. Hoboken, New Jersey: Wiley, 2016.</span></p>
</div>
<div id="ref-helfandDynamicReteamingArt2020" class="csl-entry">
<p><span class="csl-left-margin">[12] </span><span class="csl-right-inline">Heidi Helfand, <em>Dynamic Reteaming: The Art and Wisdom of Changing Teams</em>. O’Reilly Media, 2020 [Online]. Available: <a class="link" href="https://learning.oreilly.com/library/view/dynamic-reteaming-2nd/9781492061281/"  target="_blank" rel="noopener"
    >https://learning.oreilly.com/library/view/dynamic-reteaming-2nd/9781492061281/</a>. [Accessed: 11-Jan-2021]</span></p>
</div>
</div>
]]></description>
      <author>Toni Tassani</author>
    </item>
  </channel>
</rss>
