<?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 Teamleadsky on Medium]]></title>
        <description><![CDATA[Stories by Teamleadsky on Medium]]></description>
        <link>https://medium.com/@teamleadsky?source=rss-60c90b3d7a1b------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*xlTIkeCjeCzkxK1utyqRBg.png</url>
            <title>Stories by Teamleadsky on Medium</title>
            <link>https://medium.com/@teamleadsky?source=rss-60c90b3d7a1b------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 23:00:05 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@teamleadsky/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[Understanding Definition of Done]]></title>
            <link>https://medium.com/teamleadsky/understanding-definition-of-done-45b3535cf73f?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/45b3535cf73f</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[dod]]></category>
            <category><![CDATA[definition-of-done]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Thu, 27 Apr 2023 09:36:09 GMT</pubDate>
            <atom:updated>2023-04-27T09:36:09.990Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Understanding Definition of Done" src="https://cdn-images-1.medium.com/max/1024/1*vA1vGIe2aIvP9nunR6Q9Zw.png" /></figure><p>The Definition of Done (DoD) is an essential element of Agile software development, creating a shared understanding among team members of when a task or user story is considered complete. In this article, we’ll explore the benefits of having a clear DoD, its key components, and the possibility of having multiple definitions based on different types of work.</p><h3>Definitions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*js-jvpwUHe6Pf8cFNvIzJw.png" /></figure><p>It is crucial to differentiate the Definition of Done from Acceptance criteria. Acceptance criteria specify the requirements for a particular task or user story to be considered done, while the Definition of Done provides a set of criteria for any task of a certain type of work to be considered completed.</p><h3>Benefits of a Clear Definition of Done</h3><p>Having a well-defined DoD offers several advantages:</p><ul><li><strong>Improved collaboration:</strong> Team members understand what activities must be completed for a task to be considered done, eliminating ambiguity.</li><li><strong>Better quality of work:</strong> The Definition of Done typically includes requirements related to coding standards, test coverage, and documentation, ensuring high-quality output.</li><li><strong>Reduced back-and-forth:</strong> A clear Definition of Done helps to minimize misunderstandings and unnecessary discussions about task completion.</li></ul><h3>Components of the Definition of Done</h3><p>The DoD typically consists of five key elements:</p><ol><li><strong>Code quality:</strong> Adherence to coding standards and guidelines.</li><li><strong>Documentation:</strong> Compliance with requirements for technical documentation or user guides.</li><li><strong>Testing:</strong> Ensuring adequate test coverage and completion of manual or automated testing activities.</li><li><strong>Review and approval:</strong> Meeting requirements for peer review or Product Owner approval.</li><li><strong>Deployment and monitoring:</strong> Following appropriate deployment procedures and setting up monitoring and tracking.</li></ol><p>The Definition of Done should be tailored to the specific needs and characteristics of a project. For example, projects involving Python development should adhere to specific style guides for the language, while projects with accessibility requirements should include relevant user interface standards.</p><p>It’s essential to strike a balance between specificity and flexibility in the Definition of Done. Overly detailed definitions can become burdensome and hinder the team’s ability to adapt to unforeseen challenges.</p><h3>Multiple Definitions of Done</h3><p>Depending on the types of work a team handles, it’s possible to have more than one Definition of Done. For example, a research or exploration task (Spike), a data analysis task, and an engineering feature going to production may each have their unique DoD.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3bG0V3TbuCboKgHMSSNIcg.png" /></figure><p>The Definition of Done for a spike might include a well-defined research question, identification of potential solutions, a time-boxed approach, clear documentation of findings, and presentation of outcomes to the relevant audience.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pW1X3zph1DXQ7jpjb_ktEA.png" /></figure><p>In contrast, the Definition of Done for data analysis may require a clear objective, appropriate visualization, explicit mention of assumptions, explanation of the analysis approach, and presentation of outcomes to stakeholders.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qMrTlwynSDJpkbyDiwl7tw.png" /></figure><p>The Definition of Done for an engineering feature going to production will likely be more detailed, with criteria related to user interfaces, code quality, monitoring, and alerting to ensure the feature operates well in production.</p><h3>Creating a Definition of Done with Your Team</h3><p>It is crucial to have all team members and relevant stakeholders on board when creating a Definition of Done. This not only ensures that everyone is on the same page but also allows for valuable insights to be shared.</p><p>To avoid long meetings and streamline the process, consider making the process partially <strong>asynchronous</strong>. This can involve a short meeting to introduce the concept of the Definition of Done, followed by an asynchronous discussion where team members can share their ideas and criteria for the DoD, finalized by a meeting where the working version of the DoD will be created.</p><p>Keep in mind that the Definition of Done is a living document, and it will likely change and evolve over time. Make sure that the people taking part in the creation of the DoD understand that. That will help to avoid stalemates during the discussion. Be prepared to review and improve the DoD based on feedback from the participants and schedule a follow up session on reviewing and improving the Definition of Done.</p><p>Here are some drivers and restrainers that can impact the creation of a strong Definition of Done.</p><p><strong>Drivers:</strong></p><ul><li>Everyone being on the same page: Understanding the purpose and usage of the DoD is crucial for its success.</li><li>Simplicity: A simple Definition of Done with clear criteria is more likely to be used and understood by team members.</li><li>Technical expertise: Involve experienced team members or external experts to ensure that the Definition of Done is based on solid technical knowledge.</li><li>Cross-functional setup: Include representatives from all specializations to ensure that the DoD caters to the diverse needs of the team.</li></ul><p><strong>Restrainers:</strong></p><ul><li>Dominating voices: Watch out for individuals who may overshadow others in discussions, preventing diverse perspectives from being heard.</li><li>Hidden agendas: Be aware of personal interests that may affect the creation of the Definition of Done and address them accordingly.</li><li>Different visions of ideal team collaboration: It’s essential to have clear work agreements in place that outline how the team will work together. These work agreements are created during <a href="https://medium.com/teamleadsky/agile-201-team-liftoff-1c78da8bb321">Team Liftoff</a> and help facilitate the creation of a well-aligned Definition of Done.</li></ul><p>A well-defined Definition of Done plays a crucial role in successful Agile Software development, fostering improved collaboration, higher quality work, and reduced back-and-forth among team members. By involving all stakeholders, ensuring technical expertise, and maintaining a cross-functional setup, teams can create a strong Definition of Done that caters to their specific needs. It’s essential to strike a balance between specificity and flexibility while creating the Definition of Done and keep improving the DoD over time as a living document.</p><p><em>This article contains the summary of the video below partialy completed with GPT-4, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FRjIxTbPfZJA%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DRjIxTbPfZJA&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FRjIxTbPfZJA%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/b90f04468c36e47c484d663da396cd64/href">https://medium.com/media/b90f04468c36e47c484d663da396cd64/href</a></iframe><p>Find more talks, articles and tools at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=45b3535cf73f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/understanding-definition-of-done-45b3535cf73f">Understanding Definition of Done</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile 201 — User Stories]]></title>
            <link>https://medium.com/teamleadsky/agile-201-user-stories-669ae9651b80?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/669ae9651b80</guid>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[user-stories]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Sat, 11 Mar 2023 15:16:05 GMT</pubDate>
            <atom:updated>2023-03-11T15:16:05.692Z</atom:updated>
            <content:encoded><![CDATA[<h3>Agile 201 — User Stories</h3><figure><img alt="Agile 201 — User Stories" src="https://cdn-images-1.medium.com/max/960/1*6ZTAAck8pt4P71zsKfJ6cQ.jpeg" /></figure><h4>Purpose of User Stories</h4><p>User Stories are a convenient way to split the software into parts and describe it. They are useful for prioritization and stakeholder conversations. The term “feature” is often used synonymously with User Stories, but it’s important to understand that User Stories are not detailed software requirements. User Stories serve as markers or titles of software features and are always written in the language of the business. They are used to refer to a particular feature or functionality of the software system.</p><h4>User Stories Formats</h4><p>There are various formats for writing user stories. The most common one is the <strong>“As a [user], I want to [action], so that [benefit]”</strong> format:</p><figure><img alt="User Stories format" src="https://cdn-images-1.medium.com/max/1024/1*6IkGALTgONGPTttKuzXoFw.png" /></figure><p><strong>“Who? What? Why?”</strong> is another convenient way of writing User Stories:</p><figure><img alt="“Who? What? Why?” User Stories format" src="https://cdn-images-1.medium.com/max/1024/1*WScwuiqDvFeUIyD1LkaM2g.png" /></figure><p>User Stories consist of three parts: the <strong>User</strong>, the <strong>Action</strong>, and the <strong>Goal</strong>.</p><h4>Acceptance Criteria</h4><p>Specifying Acceptance criteria is an important part of creating User Stories. Acceptance criteria specify the conditions that must be met for the User Story to be considered complete and implemented successfully. Acceptance criteria are used to ensure that the development team and stakeholders have a shared understanding of what the User Story entails and what needs to be delivered. They also provide a way to validate that the User Story has been completed and that the functionality it describes is working as intended.</p><p>Acceptance criteria should be testable via a “binary test”, answering “yes” or “no” to a question whether an Acceptance criteria is met.</p><figure><img alt="Acceptance Criteria" src="https://cdn-images-1.medium.com/max/1024/1*0nCIJ-LR1Q6VMVNXXYnB_g.png" /></figure><p>Acceptance criteria can be also conveniently specified in the format used in Behavior-driven Design. Behavior-driven Design (BDD) is a software development methodology that is focused on defining and testing the behavior of software systems using plain language descriptions of system behavior. BDD builds on the principles of Test-Driven Development (TDD) and Domain-Driven Design (DDD), and is based on the idea that software systems should be designed and tested based on their behavior, rather than their implementation details.</p><figure><img alt="Behavior-driven design format" src="https://cdn-images-1.medium.com/max/1024/1*b_qy4Y26cN7TF8r8EkvbBA.png" /></figure><h4>Splitting User Stories</h4><p>Deciding along which lines to split the User Stories can be quite challenging. However there are helpful best practices to follow, e.g. <a href="https://xp123.com/articles/twenty-ways-to-split-stories/">Twenty Ways to Split User Stories</a>. Whatever approach is chosen, it’s important to ensure that each User Story is still able to provide value to the end user. By splitting User Stories into smaller, more manageable pieces, development teams can ensure that they can prioritize work more effectively, reduce risks and dependencies.</p><p>The <strong>INVEST criteria</strong> is a helpful acronym that defines the characteristics of a good user story:</p><ul><li><strong>I</strong> stands for Independent, which means that each user story should be self-contained and able to be worked on and tested independently:</li><li><strong>N</strong> stands for Negotiable, which means that user stories should not be overly prescriptive, allowing room for discussion and different ways of implementing the story to deliver the intended value to the user.</li><li><strong>V</strong> stands for Valuable, which means that each user story should provide value to the end user or customer.</li><li><strong>E</strong> stands for Estimable, which means that each user story should be able to be estimated in terms of its level of effort or complexity.</li><li><strong>S </strong>stands for Small, which means that user stories should be broken down into small, manageable pieces.</li><li><strong>T</strong> stands for Testable, which means that each user story should be able to be tested to ensure that it has been implemented correctly.</li></ul><p>By following these INVEST criteria, development teams can ensure that their user stories are clear, concise, and effective.</p><h4>Writing Good User Stories</h4><p>Let’s review some drivers and restrainers to writing good User Stories. Creating User Stories is a collaborative effort between the Product Owner, stakeholders and the development team. Having good communication, good working relationships, and diverse team composition helps create better User Stories. Diverse team composition helps to write better User Stories as the team members can provide various additional perspectives on creating value for the users.</p><p>Lack of alignment, failure to prioritize business goals, and lack of time for refinement are some of the factors that stand in the way of creating good User Stories. The Product Manager must invest enough time in refining user stories and ensure that the stakeholders understand the benefits and prioritization of the User Stories.</p><p>It is important that the Product Manager remembers that the User Stories are a tool for conversation, therefore it is important that all the participants are aligned about the content of the stories, which takes time to achieve.</p><p>In conclusion, User Stories are an essential aspect of Agile software development methodology. It is crucial to follow the invest criteria and choose a suitable splitting pattern. Creating User Stories is a collaborative effort, and having good communication and diverse team composition can help create better User Stories. It is also essential to invest enough time in refining User Stories and ensuring that stakeholders understand their benefits and prioritization.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FV-xkL5_Ia9A%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DV-xkL5_Ia9A&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FV-xkL5_Ia9A%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/7a6cc1a6829b66a65bffdd001ecc4eec/href">https://medium.com/media/7a6cc1a6829b66a65bffdd001ecc4eec/href</a></iframe><p>Find more talks, articles and Agile tools at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=669ae9651b80" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/agile-201-user-stories-669ae9651b80">Agile 201 — User Stories</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Re-think Decision-making!]]></title>
            <link>https://medium.com/teamleadsky/re-think-decision-making-f17897ebfa1a?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/f17897ebfa1a</guid>
            <category><![CDATA[decision-making]]></category>
            <category><![CDATA[decision-making-process]]></category>
            <category><![CDATA[decision-making-tools]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Mon, 06 Mar 2023 10:25:03 GMT</pubDate>
            <atom:updated>2023-03-06T10:28:33.173Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Re-think Decision-making!" src="https://cdn-images-1.medium.com/max/1024/1*4lmWpbsQcRa3G_wXpiYdQw.png" /></figure><p>Karen Schmidt is the co-creator of <a href="https://overthefence.com.de/">Over The Fence</a> together with Frank Habermann. Over The Fence is a community that creates thinking tools, which help people think better about management decisions. In her talk Karen shares insights on decision-making and how Over The Fence’s tools can help organizations make better decisions.</p><h4>Fast and Slow Thinking</h4><p>Karen started with the concept of <a href="https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow">fast and slow thinking</a>, which she attributed to Daniel Kahneman, a Nobel Prize-winning psychologist. She explained that our brains are wired to think fast and intuitively, which is useful for routine situations. However, when it comes to making complex decisions, we need to think slow, which means taking the time to observe without judgment, ask questions, and reflect before making a decision.</p><p>She then discussed the top three limiting beliefs in decision-making, which are :</p><ul><li>Decision-makers are defined in the organizational chart,</li><li>Anyone who is involved in a decision-making process needs to decide, and</li><li>In well-organized structures decisions are always made together.</li></ul><p>Karen emphasized the need to question these assumptions and to take a more nuanced approach to decision-making, which involves a better understanding of roles in the decision-making process.</p><h4>The Decision-Making Process</h4><p>Karen presented a simple visualization of the decision-making process, which involved identifying the situation or problem, determining the desired outcome, exploring options, making a decision, and implementing the decision. She highlighted the blind spots in this process, such as the tendency to skip steps, the influence of personal biases, and the difficulty in reaching a consensus when working in groups.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L4ZY3keVUswycqmpx9YbhA.png" /></figure><p>Finally, Karen emphasized the need for a new perspective on decision-making, which involves questioning assumptions, understanding roles, and taking a more nuanced approach. She emphasizes the importance of having a practical perspective on decision-making and explains that a good decision is one that can be implemented. To achieve this, one needs to have clarity on the desired effect of the decision and the results that would qualify as a means to this end.</p><h4>The Decision Hats Framework</h4><p>Talking about the decision-making process and the importance of involving relevant stakeholders, Karen introduces the “Decision Hats” framework. The framework includes six roles for decision-making: the Owner, the Facilitator, Experts, Implementers, Users, and the Decision-maker. Karen explains that each decision-making process needs these roles, and individuals can have different hats, meaning they can play different roles.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pk-YUAfn45uNRLjbzlaZtA.png" /></figure><p>She highlights three key lessons: the quality of a decision depends on the quality of the decision-making process, a good decision-making process needs the participation of relevant stakeholders, and participating in a decision-making process is not the same as making the decision.</p><h4>Decision-making Canvas</h4><p>Karen also introduced the concept of a decision-making canvas, which is a tool to help clarify the decision-making process. The canvas is divided into sections, each with a set of questions that need to be answered before a decision can be made. The questions are designed to help decision-makers understand the purpose and desired outcome of the decision, as well as the potential impact and consequences of different options.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wmqp7A2EHgPPuRdWZJbeCQ.png" /></figure><p>Karen emphasized the importance of the decision-making canvas in helping to ensure that decision-makers have a shared understanding of the decision need, and that all stakeholders have an opportunity to participate in the decision-making process. The canvas is just one of many tools available on Over the Fence website, which are all offered under a Creative Commons license for anyone to use and adapt as needed: <a href="https://overthefence.com.de/tools/">https://overthefence.com.de/tools/</a></p><h4>Key Lessons</h4><p>Karen emphasizes the importance of self-reflection before criticism and invites individuals to use the decision canvas and decision story to gain clarity on the decision need. She also suggests that individuals should reflect on the potential confusions regarding the goals and the decision, who should be involved, and what the outcome of the decision is.</p><p>Karen also discusses the importance of time and its impact on decision-making. She explains the significance of considering the costs or consequences of delay when making decisions. She recommends inviting stakeholders, users, and implementers to give their opinions and to reflect on the other roles involved in decision-making.</p><p>The tools and frameworks offered by Over The Fence, such as the decision canvas and decision hats, provide practical guidance for individuals and organizations seeking to make better decisions. By adopting a more nuanced approach to decision-making, and understanding the importance of a well-designed decision-making process, individuals and organizations can navigate complex challenges with greater clarity and effectiveness.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FJ99fMvqHTgE%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DJ99fMvqHTgE&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FJ99fMvqHTgE%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/12223a54792ea9c2f8a923519a7f0de6/href">https://medium.com/media/12223a54792ea9c2f8a923519a7f0de6/href</a></iframe><p>Find more talks, articles and Agile tools at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f17897ebfa1a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/re-think-decision-making-f17897ebfa1a">Re-think Decision-making!</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Agile 201 - Team Liftoff]]></title>
            <link>https://medium.com/teamleadsky/agile-201-team-liftoff-1c78da8bb321?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/1c78da8bb321</guid>
            <category><![CDATA[team-leader]]></category>
            <category><![CDATA[project-management]]></category>
            <category><![CDATA[team-liftoff]]></category>
            <category><![CDATA[engagement]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Thu, 16 Feb 2023 10:30:05 GMT</pubDate>
            <atom:updated>2023-02-16T10:38:26.039Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mXBtX6FRP6QnffYLppr4jA.png" /></figure><p>One of the key factors that determine the success of any project or team is the quality of collaboration among team members. A well-coordinated team is more likely to achieve its goals, deliver value, and meet the expectations of stakeholders. However, creating and sustaining effective collaboration is not a given; it requires intentional effort, alignment, and shared purpose. That’s where team Liftoff comes in.</p><p>Team Liftoff is an activity that brings people in a team and stakeholders together. It is a way of launching a new team or starting a team on a new project, or even re-energizing an existing team. The goal of team Liftoff is to provide a clear understanding of the business context and the impact of the team’s work, better interpersonal alignment, and create better personal connections within the team.</p><p>Liftoff is a structured and participatory process that helps teams and stakeholders align on their goals, vision, ways of working, and shared values. The term “Liftoff” has several synonyms, such as inception, kick-off, or team restart, but the underlying idea is the same: to launch the team towards a common goal and create a sense of ownership, motivation, and trust.</p><h4>Liftoff Participants</h4><p>The presence of the team members and an executive sponsor is essential for the Liftoff. The sponsor can provide the team with the business vision, explain why their work matters, and what the organization is trying to achieve with their help. The executive sponsor can also ensure that the senior management team is committed to the objectives that the team receives and the solutions they are working on will end up in production. It is sufficient if the executive sponsor joins the Liftoff for a short time at the beginning of the event, shares their vision and answers questions of the team members.</p><h4>Agile Chartering</h4><p>Agile Chartering is an essential part of team Liftoff, which is aimed at discussing and aligning on things such as what kind of work the team is doing, what outcomes they are expecting, what the purpose of the team is, and how they are going to achieve that purpose. It is important to note that agile chartering has two steps, and the first step is preparation. The Liftoff facilitator and leadership need to prepare some structure and drafts, so the team members can discuss and build on top of that. That helps to achieve focus and save time, however it is important that the team members co-create the final working version. As well it is important to make sure everyone involved understands that the resulting Agile Charter is not carved in stone, but is there to be reviewed and improved over time collaboratively.</p><h4>Liftoff Agenda</h4><p>Here is an example agenda of a Liftoff:<br>● Executive Sponsor briefs on the business vision.<br>● Core team members, who they are, how will they contribute?<br>● How do we contribute to the vision as a team? (Team Mission)<br>● Relations with the stakeholders.<br>● Boundaries and interactions with the other teams.<br>● The Drivers and Restrainers to our work. The ideal collaboration.<br>● Closure.</p><p>Below are the examples of some useful approaches for the activities of this agenda.</p><h4>Power-interest Grid</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*J7AxmaCuNHaf8inQOHJtcA.png" /><figcaption><a href="https://www.romanpichler.com/blog/stakeholder-engagement-analysis-power-interest-grid/">https://www.romanpichler.com/blog/stakeholder-engagement-analysis-power-interest-grid/</a></figcaption></figure><p>The Power-interest Grid is a tool used to classify stakeholders based on their level of power and interest in a project or initiative. The grid helps identify stakeholders that are critical to the project’s success and decide on the type of collaboration the team members need to engage into with different stakeholders.</p><p>The power axis of the grid is based on the stakeholder’s level of power, which can be either high or low. Power refers to the ability of the stakeholder to influence the project’s outcome. This can be based on factors such as their position within the organization, their level of expertise, or their ability to mobilize resources.</p><p>The interest axis of the grid is based on the stakeholder’s level of interest, which can also be either high or low. Interest refers to the stakeholder’s level of concern or involvement in the project. This can be based on factors such as how the project will impact their job, their department or their organization.</p><p>Based on their level of power and interest, stakeholders can be classified into one of four categories:</p><ol><li><strong>Players </strong>(high power, high interest ) — These stakeholders are critical to the project’s success and require close management. They are typically engaged as active participants in the project and can provide valuable insights and support.</li><li><strong>Context Setters</strong> (high power, low interest )— These stakeholders have the ability to influence the project’s outcome, but may not have a personal interest in the project. Team leaders keep them informed and updated on the project’s progress, but may not require their active participation.</li><li><strong>Subjects </strong>(low power, high interest) — they have a personal interest in the project but may not have the power to influence the project’s outcome. Team members should keep them informed and engaged to ensure their support and buy-in.</li><li><strong>Crowd </strong>(low power, low interest) — is not critical to the project’s success and require minimal management. It is enough to ensure they are informed about the project’s progress, but may not require any active engagement.</li></ol><h4>Ideal State</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6obkssRWeqNq46KSx9gwxA.png" /><figcaption><a href="https://teamleadsky.com/remote-team-agile-coaching">teamleadsky.com/coaching</a></figcaption></figure><p>Aligning on the Ideal State of teamwork is an efficient way to set a developmental goal to the team. It is a two-step process starting with a <a href="https://gamestorming.com/force-field-analysis/">Force Field Analysis</a> session with the team members to identify the <em>drivers </em>and <em>restrainers </em>to their work. Next the team members discuss where they want to get and what kind of collaboration they want to have in the team by developing the existing drivers, introducing the drivers that are currently not present in the work of the team and eliminating restrainers. This process helps in aligning on a common vision of the ideal state of team collaboration, which also helps in designing the ways of working with the team members.</p><p>This video shows how to quantify the developmental goal:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fa5SJPpkwj40%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Da5SJPpkwj40&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fa5SJPpkwj40%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9c5528b2edf194f1bc6997a3bb7b235b/href">https://medium.com/media/9c5528b2edf194f1bc6997a3bb7b235b/href</a></iframe><h4>Team Topologies</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*es4C443gDgHxWjt8Iuc15A.png" /><figcaption><a href="https://teamtopologies.com/">https://teamtopologies.com/</a></figcaption></figure><p>Team Topologies is an efficient approach discussing boundaries and interactions with the members of the other teams. It is a framework for organizing and optimizing teams in order to improve delivery and streamline collaboration. The framework defines four fundamental team types: Stream-aligned teams, Enabling teams, Complicated-subsystem teams, and Platform teams. Each team type is designed to address specific organizational challenges and support specific goals. In addition, the framework also provides a set of patterns for team interaction, communication, and decision-making.</p><p>This video provides a review of the Team Topologies framework:</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1qCptJHMPgg%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1qCptJHMPgg&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1qCptJHMPgg%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/4f1b5b6c0d40038bf0050e1d14cb1210/href">https://medium.com/media/4f1b5b6c0d40038bf0050e1d14cb1210/href</a></iframe><h4>Keeping the Liftoff Alive</h4><p>Everything created during the team Liftoff is just the first working version and is created to inspect and improve together with the team members over time. It is important to keep track of the drivers and restrainers identified during Force Field Analysis and make sure that the team is developing towards it’s agreed Ideal State. That supports the focus on eliminating the issues and creating an environment that fosters the development of the drivers needed for the successful work of the team. As well when changes happen in the organizational context or business environment it is the time to consider organizing another Liftoff to make sure that the shared understanding of the team purpose and vision and the ways of working match the context in which the team operates.</p><p><em>This article contains some definitions and partial summary of the video below completed with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fjo2R7GdYC0k%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Djo2R7GdYC0k&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2Fjo2R7GdYC0k%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a70b9c8df8fc8da728737e6a1ef79cdb/href">https://medium.com/media/a70b9c8df8fc8da728737e6a1ef79cdb/href</a></iframe><p>Find more talks, articles and tools at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1c78da8bb321" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/agile-201-team-liftoff-1c78da8bb321">Agile 201 - Team Liftoff</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Service Blueprints for User-Centric Team Setup]]></title>
            <link>https://medium.com/teamleadsky/service-blueprints-for-user-centric-team-setup-e9b8f0d98aad?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9b8f0d98aad</guid>
            <category><![CDATA[organizational-design]]></category>
            <category><![CDATA[organizational-change]]></category>
            <category><![CDATA[user-centered-design]]></category>
            <category><![CDATA[service-blueprint]]></category>
            <category><![CDATA[team]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Sun, 15 Jan 2023 13:02:33 GMT</pubDate>
            <atom:updated>2023-01-15T13:03:04.318Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Service Blueprints for User-Centric Team Setup" src="https://cdn-images-1.medium.com/max/1024/1*PlGE9IjgmN6iOsvkkPs2XQ.png" /></figure><p>In this talk Christoph Steinlehner, strategic Product discovery and design consultant is discussing the use of Service Blueprints as a tool to improve team alignment with customer journeys and creating user-centric team setups</p><h4>What is a Service Blueprint</h4><p>A Service Blueprint is a diagram that illustrates the relationships between different service components, people, props, physical or digital evidence, and processes that are directly linked to touchpoints in a specific customer journey. The concept of Service Blueprints was first introduced by G. Lynn Shostack, who intended them to be used as a tool for management and control of processes. Christoph then uses an example of his own customer journey of a broken watch to show how Service Blueprints can be used to understand the customer journey, including the evidence and interactions of the process, as well as the internal workflows of the company.</p><h4>Use of Service Blueprints</h4><p>Christoph encourages the use of Service Blueprints to improve the customer journey and align teams with customer journeys through discussions. Christoph suggests starting small, by identifying bottlenecks and making small adjustments, instead of undergoing a major re-organization. By utilizing Service Blueprints, teams can be aligned to the user journey and dependencies between teams can be identified. This allows for the creation of clear team missions and visions, and makes it simpler to split teams as the organization grows.</p><h4>Additional suggestions</h4><p>Christoph also suggests using service blueprints during organizational transformations and when there are many dependencies between teams. Christoph highlights that Service Blueprints can function as an “x-ray” to reveal the internal workflows of a company and their relationship to the end customer. He encourages the use of Service Blueprints for discussions and for the improvement of the overall customer journey. He also suggests enhancing Service Blueprints with the information on errors and comments to identify bottlenecks in flow of information. He encourages teams to begin today or tomorrow by taking a pen and paper or using online whiteboarding software to write down the user story.</p><p>In conclusion, Service Blueprints can be an effective tool for improving team alignment with customer journeys and creating user-centric team setups. Christoph suggests using them during organizational transformations and when there are many dependencies between teams. By utilizing Service Blueprints, teams can align to the user journey, identify dependencies, and create clear team missions and visions. It’s a powerful tool that can help organizations to understand the customer journey and internal workflows of a company, and ultimately improve the overall customer experience.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FDz_StcH_Xu0%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DDz_StcH_Xu0&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FDz_StcH_Xu0%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/3ab754c9b6e126ce6b3f8c9883511f1f/href">https://medium.com/media/3ab754c9b6e126ce6b3f8c9883511f1f/href</a></iframe><p>Find more talks, articles and tools for Agile Retrospectives at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9b8f0d98aad" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/service-blueprints-for-user-centric-team-setup-e9b8f0d98aad">Service Blueprints for User-Centric Team Setup</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI, DATA SCIENCE — Why Culture Matters?]]></title>
            <link>https://medium.com/teamleadsky/ai-data-science-why-culture-matters-8d24fdc4e2a3?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/8d24fdc4e2a3</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[machine-learning]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-driven]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Mon, 09 Jan 2023 15:18:54 GMT</pubDate>
            <atom:updated>2023-01-09T15:18:54.869Z</atom:updated>
            <content:encoded><![CDATA[<h3>AI, DATA SCIENCE — Why Culture Matters?</h3><figure><img alt="AI, DATA SCIENCE — Why Culture Matters?" src="https://cdn-images-1.medium.com/max/1024/1*1mVdTm86ksCe8MlUnaeCsw.png" /></figure><p>In this talk Dr. Stylianos Kampakis explains why organizations should become data-centric and what are the crucial steps to getting there. He covers the differences between data-centric, data-informed, and data-driven and explains what role does culture play in the adoption of AI and Data Science.</p><h4>The Importance of Data Science Culture</h4><p>Dr. Stylianos Kampakis has been involved in the field of Data Science and AI for over 10 years and has written a book on the topic. He believes that Data Science culture can be broken down into three levels: management, employee, and organizational. An organization that is data informed uses data dashboards and other tools to make decisions, while a data-driven organization uses Data Science and AI in an automated way to make decisions. However, it is important for organizations to have the right culture in order to use data effectively and avoid false conclusions. Stylianos also discusses the importance of having a data literacy program and building a data-driven culture from the bottom up.</p><h4>Overcoming Resistance to Data Science</h4><p>Dr. Kampakis discusses the importance of understanding why an organization wants to use Data Science and AI, and the different types of resistance to change that may arise. He identifies cultural resistance to change as a common issue, particularly in large organizations with multiple layers of management that have not previously had much experience with quantitative analysis. Personal resistance to change, in which individuals do not see a personal benefit in helping to implement change, is also a common issue. In order to overcome these types of resistance, it is important to have a data literacy program in place and to build a data-driven culture from the bottom up.</p><h4>Challenges of Using Agile frameworks in Data Science Projects</h4><p>Stylianos discusses the challenges of using Agile frameworks in Data Science projects, as Data Science often operates in a more non-linear way than software development. This can lead to frustration for data scientists when they have to go through daily stand-ups and report progress, as they may be experimenting with different approaches that may take weeks or months to yield results. Stylianos believes that one way to address this issue is for executives and managers to take ownership of Data Science through education and understanding, and to work with people they trust. He also suggests creating a data literacy program and building a data-driven culture from the bottom up.</p><p>In summary, Dr. Kampakis believes that it is important for organizations to have the right culture in order to effectively use data and avoid false conclusions, and suggests implementing a data literacy program and building a data-driven culture from the bottom up in order to overcome cultural and personal resistance to change. He also highlights the challenges of using Agile frameworks in Data Science projects and suggests that executives and managers can address this issue by taking ownership of Data Science through education and understanding, and working with trusted individuals.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FipNk2nbHo2Q%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DipNk2nbHo2Q&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FipNk2nbHo2Q%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/48b386f3b18455a9c943c72bcb26ccbd/href">https://medium.com/media/48b386f3b18455a9c943c72bcb26ccbd/href</a></iframe><p>Find more talks, articles and tools for Agile Retrospectives at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8d24fdc4e2a3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/ai-data-science-why-culture-matters-8d24fdc4e2a3">AI, DATA SCIENCE — Why Culture Matters?</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Self-reflective Retrospective]]></title>
            <link>https://medium.com/teamleadsky/the-self-reflective-retrospective-46a57505cbd0?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/46a57505cbd0</guid>
            <category><![CDATA[self-reflection]]></category>
            <category><![CDATA[agile-retrospective]]></category>
            <category><![CDATA[sprint-retrospective]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Mon, 28 Nov 2022 10:42:01 GMT</pubDate>
            <atom:updated>2023-01-08T17:07:23.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="The Self-reflective Retrospective" src="https://cdn-images-1.medium.com/max/1024/1*pyIwnnC3h2Qk9XisNyqCXg.png" /></figure><p>Faye Tsampardouka is a Head of Agile Delivery at MORO Tech and a software engineer with a passion for Agile methodologies and helping teams reach their full potential.</p><h4>Importance of Retrospectives for Building Self-Managed Teams</h4><p>Faye believes that self-managed teams, which involve a shared sense of ownership and contribution among team members, are more motivated, efficient, and cost-effective than traditionally managed teams. Faye emphasizes the importance of self-awareness for self-driven individuals and incorporating self-reflection into team dynamics for building successful self-managed teams. Faye also sees Retrospectives, a process for continuously improving team performance through reflection, as crucial for fostering self-awareness and building self-managed teams.</p><h4>Self-Reflective Retrospective Process</h4><p>Faye suggests using a self-reflective Retrospective process, which involves two columns for reflecting on past events and envisioning alternative actions and behaviors in the future, to build self-awareness and promote positive behaviors in teams, particularly those going through a healing phase. She recommends asking team members to consider specific situations from the past and how they could have acted differently, either as individuals or as a team. Faye advises starting with positive behaviors and focusing on changes that team members want to make for themselves and the group. She also believes that coaching through example and reflection is more effective than correction.</p><h4>Templates and Use of Self-Reflective Retrospective Process</h4><p>Faye has created templates for this self-reflective Retrospective process in Miro and provided instructions on how to access them. She believes that this process can be particularly useful for coaches, managers, and HR professionals, and suggests using it as a coaching exercise for individuals with a trusting relationship in place.</p><p>With her background in software engineering and Agile methodologies, Faye has developed a wealth of knowledge on how to build and support successful, self-managed teams. By emphasizing the importance of self-awareness and self-reflection, Faye has found that teams are able to foster a sense of ownership and contribution, leading to increased motivation, efficiency, and cost-effectiveness. Through the use of Retrospectives, Faye has been able to help teams continuously improve their performance and build strong, self-managed teams. By sharing her templates and knowledge with others, Faye is able to help other professionals and teams benefit from her expertise and insights.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2Fr12A2JzSswY&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3Dr12A2JzSswY&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2Fr12A2JzSswY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/1095752b56c988d7107e3e6dacd19024/href">https://medium.com/media/1095752b56c988d7107e3e6dacd19024/href</a></iframe><p>Find more talks, articles and tools for Agile Retrospectives at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46a57505cbd0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/the-self-reflective-retrospective-46a57505cbd0">The Self-reflective Retrospective</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TEAM CONFLICTS RESOLUTION — What is my conflict mode?]]></title>
            <link>https://medium.com/teamleadsky/team-conflicts-resolution-what-is-my-conflict-mode-d9c3be7f3eab?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/d9c3be7f3eab</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[thomas-kilmann]]></category>
            <category><![CDATA[effective-communication]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[conflict-resolution]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Mon, 21 Nov 2022 17:45:53 GMT</pubDate>
            <atom:updated>2023-01-08T16:47:54.390Z</atom:updated>
            <content:encoded><![CDATA[<h3>TEAM CONFLICTS RESOLUTION — What is my conflict mode?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OixHpesEHp1FeKfnlSnPFw.png" /></figure><p>Whenever we collaborate closely in a team, we will face different opinions, working styles, and preferences. Team work thus requires the ability to negotiate effectively and reach mutual gain solutions for the people involved. Becoming aware of ones own style when faced with conflict is a great tool for becoming an effective negotiator. In this talk <a href="http://www.annabernhardt.de/index.html">Anna Bernhardt</a> explains the great model from Thomas &amp; Kilman on conflict modes.</p><p>Anna is a trained psychologist and certified mediator with a focus on conflict resolution. She has a background in the Harvard negotiation approach and has experience as a facilitator, coach, and Design Thinking trainer.</p><h4>The Importance of Managing Conflict</h4><p>Anna believes that conflict is a normal part of working and living with others, and that it is important to manage conflicts well in order to avoid negative consequences such as decreased productivity, increased turnover, and decreased motivation, creativity, and decision-making. Instead, Anna suggests harnessing the benefits of diversity through negotiation in order to achieve win-win outcomes and personal and organizational growth. However, she notes that people often struggle with being either too empathetic or too assertive in conflicts, and suggests finding a balance in order to effectively navigate negotiations.</p><h4>The Conflict Mode Model</h4><p>Anna shares the conflict mode model developed by Thomas and Killman, which is a tool for increasing clarity and self-reflection in conflicts by considering one’s level of empathy and assertion. The model maps out five different conflict styles ranging from avoiding the conflict altogether to collaborating and finding a win-win solution that fits both parties’ interests. Anna emphasizes the importance of finding flexibility and situational cleverness in conflicts, rather than falling into an automatic stress response. She also notes that there can be constructive and destructive ways to compromise in a conflict.</p><h4>Increasing Clarity and Flexibility in Conflicts and Negotiations</h4><p>Anna suggests several steps for increasing clarity and flexibility in conflicts and negotiations. These include self-reflection on one’s own tendencies in conflicts, taking time to understand the reasons behind those tendencies, and seeking training opportunities in daily life to practice different conflict modes. She also notes the value of this process for personal growth, improved relationships, and organizational effectiveness, and suggests that it can improve the overall quality of life. She also notes the importance of proactivity and situational awareness in conflicts.</p><p>To sum it up, Anna’s approach to conflict resolution is centered on the idea that conflicts are a normal and inevitable part of working and living with others, but that they can be managed effectively in order to avoid negative consequences and instead achieve positive outcomes. Through self-reflection, training, and the use of tools like the conflict mode model, individuals and organizations can increase their clarity, flexibility, and proactivity in conflicts, leading to improved relationships and effectiveness.</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F-3OuONqCbsw%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D-3OuONqCbsw&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F-3OuONqCbsw%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/28815cbe155fdd9157309b6f6e0ce836/href">https://medium.com/media/28815cbe155fdd9157309b6f6e0ce836/href</a></iframe><p>Find more talks, articles and tools for Agile Retrospectives at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d9c3be7f3eab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/team-conflicts-resolution-what-is-my-conflict-mode-d9c3be7f3eab">TEAM CONFLICTS RESOLUTION — What is my conflict mode?</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s Retro got to Doodle with it?]]></title>
            <link>https://medium.com/teamleadsky/whats-retro-got-to-doodle-with-it-bbb081cf43c7?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/bbb081cf43c7</guid>
            <category><![CDATA[facilitation]]></category>
            <category><![CDATA[agile-coaching]]></category>
            <category><![CDATA[agile-retrospective]]></category>
            <category><![CDATA[sprint-retrospective]]></category>
            <category><![CDATA[template]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Sun, 13 Nov 2022 18:41:13 GMT</pubDate>
            <atom:updated>2023-01-08T16:45:51.467Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="What’s Retro got to Doodle with it?" src="https://cdn-images-1.medium.com/max/1024/1*NpwfqdREwouvYZdvHFzDHw.png" /></figure><p>In this talk Steven Sampson-Jones explains how we creates an immersive Retrospective experience, by introducing graphic and visual facilitation techniques.</p><p>Steven has a passion for drawing and uses it as a form of storytelling. In this talk he wants to share the benefits of using visual skills, whether through drawing or using stock images, in Retrospectives and will demonstrate some of his favorite boards, including a sneak peek of a Harry Potter themed one.</p><p>Steven states it is important to create engaged Retrospectives to keep team members interested and to allow for an opportunity to inspect and adapt team dynamics and work processes. During the pandemic, virtual whiteboarding tools have helped him maintain a sense of team socialization and build strong team relationships through fun, tailored Retrospectives.</p><h4>Tips for Creating Engaging Retrospectives</h4><p>Steven believes that a fun Retrospective is a good Retrospective and puts effort into storyboarding and tailoring his workshop to fit the team he is working with. He recommends celebrating microcultures and creating themes based on holidays, shared interests, or specific hobbies and interests of team members. He also emphasizes the importance of building empathy and psychological safety in Retrospectives through prompts, such as favorite foods or weekend activities, and the use of the Prime Directive.</p><h4>Visual Aids and Props in Retrospectives</h4><p>Steven suggests using visual aids, like drawings or diagrams, to facilitate discussion and encourage participation from introverted team members. Steven also recommends using props, like toy figurines or candy, to break the ice and make the Retrospective more interactive and engaging.<br>Steven suggests using visual aids and props to encourage participation and build empathy among team members. He also recommends using themes and drawing inspiration from various sources to make retrospectives more engaging.</p><h4>Additional Tips for Successful Retrospectives</h4><p>In addition, Steven recommends including a time box, an icebreaker, and a way to capture and prioritize action items in Retrospectives. He emphasizes the importance of creating a safe and welcoming environment and suggests using tools like Miro or Mural, along with images or icons, to make Retrospectives more interactive and visually appealing.</p><p>Steven’s approach to Retrospectives is to make them fun and engaging in order to facilitate open and honest communication within the team. By using visuals he creates an interactive and welcoming environment that promotes psychological safety and helps team members build empathy with one another. Through these efforts, Steven is able to facilitate meaningful discussions that allow for the inspection and adaptation of team dynamics and work processes.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FuTIku9xaAZU&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DuTIku9xaAZU&amp;image=http%3A%2F%2Fi.ytimg.com%2Fvi%2FuTIku9xaAZU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/c2678ef8df2eff73d0bd7bfaa79373f2/href">https://medium.com/media/c2678ef8df2eff73d0bd7bfaa79373f2/href</a></iframe><p>Find more talks, articles and tools for Agile Retrospectives at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bbb081cf43c7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/whats-retro-got-to-doodle-with-it-bbb081cf43c7">What’s Retro got to Doodle with it?</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to navigate VIRTUAL DISTANCE to build INFECTIOUS ACCOUNTABILITY]]></title>
            <link>https://medium.com/teamleadsky/how-to-navigate-virtual-distance-to-build-infectious-accountability-b87b1b75de35?source=rss-60c90b3d7a1b------2</link>
            <guid isPermaLink="false">https://medium.com/p/b87b1b75de35</guid>
            <category><![CDATA[remote-work]]></category>
            <category><![CDATA[remote-team]]></category>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[team-building]]></category>
            <category><![CDATA[remote-working]]></category>
            <dc:creator><![CDATA[Teamleadsky]]></dc:creator>
            <pubDate>Sun, 13 Nov 2022 18:35:47 GMT</pubDate>
            <atom:updated>2023-01-08T16:43:39.771Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="How to navigate VIRTUAL DISTANCE to build INFECTIOUS ACCOUNTABILITY" src="https://cdn-images-1.medium.com/max/1024/1*T_123tmZ6NHqOEdgOHCWVQ.png" /></figure><p>Alison JY Lee is a Leadership Coach and Organizational Psychologist, and in her talk she discusses how to navigate virtual distance and build infectious accountability in virtual teams.</p><h4>Defining Virtual Distance and Infectious Accountability</h4><p>Virtual Distance refers to the psychological distance that exists between individuals in a virtual or remote team, and Infectious Accountability refers to the ability of individuals in a team to hold each other accountable for their actions and commitments in a way that inspires others to do the same.</p><p>Alison explains that trust is a key ingredient in building relationships that motivate team members to embrace accountability. She introduces the concept of “ Virtual Distance”, which can hinder the development of trust and relationships in a team. Alison argues that it is important to understand the root cause of accountability issues in a team and suggests evidence-based strategies for closing Virtual Distance and improving trust.</p><h4>Understanding and Closing Virtual Distance</h4><p>Alison explains that Virtual Distance is made up of three categories:</p><ul><li>Physical Distance,</li><li>Operational Distance, and</li><li>Affinity Distance.</li></ul><p>Physical distance refers to the geographic and temporal distance between team members, Operational Distance refers to processes that facilitate or hinder team collaboration, and Affinity Distance refers to the depth of connections and relationships between team members. Alison argues that affinity distance has the greatest impact on team outcomes such as accountability, innovation, and performance.</p><h4>Improving Virtual Distance Within a Team</h4><p>Alison is discussing strategies for improving Virtual Distance within a team. She has provided a list of questions that can be used to assess the Virtual Distance within a team and has suggested solutions for addressing gaps in each of the three categories of Virtual Distance: Physical Distance, Operational Distance, and Affinity Distance. These solutions include creating a team name and shared values, using a game scoreboard to reinforce team values, highlighting interdependencies within the team, and giving monthly reports on team projects.</p><p>In conclusion, Alison’s talk highlights the importance of understanding and addressing Virtual Distance within virtual teams in order to build trust, relationships, and accountability. She provides practical strategies for improving Virtual Distance and emphasizes the benefits of in-person meetings for building strong and effective virtual teams.</p><p><em>Teamleadsky has summarized this talk in part with GPT-3, OpenAI’s large-scale language-generation model.</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FpQrXQ8F5uGk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DpQrXQ8F5uGk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FpQrXQ8F5uGk%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/99be1feccb87794114d7b23896c02c38/href">https://medium.com/media/99be1feccb87794114d7b23896c02c38/href</a></iframe><p>Find more talks, articles and tools for Agile Retrospectives at <a href="https://teamleadsky.com/talks">Teamleadsky</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b87b1b75de35" width="1" height="1" alt=""><hr><p><a href="https://medium.com/teamleadsky/how-to-navigate-virtual-distance-to-build-infectious-accountability-b87b1b75de35">How to navigate VIRTUAL DISTANCE to build INFECTIOUS ACCOUNTABILITY</a> was originally published in <a href="https://medium.com/teamleadsky">Teamleadsky</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>