<?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 Shiraz Rehmani on Medium]]></title>
        <description><![CDATA[Stories by Shiraz Rehmani on Medium]]></description>
        <link>https://medium.com/@shiraz.rehmani?source=rss-93520a51adc6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*8PWxFoi2PP7fzOlUV2rlnQ.jpeg</url>
            <title>Stories by Shiraz Rehmani on Medium</title>
            <link>https://medium.com/@shiraz.rehmani?source=rss-93520a51adc6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 08:54:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shiraz.rehmani/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[Addressing Five Dysfunctions in SCRUM]]></title>
            <link>https://medium.com/@shiraz.rehmani/addressing-five-dysfunctions-in-scrum-1285adec7d4d?source=rss-93520a51adc6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1285adec7d4d</guid>
            <dc:creator><![CDATA[Shiraz Rehmani]]></dc:creator>
            <pubDate>Mon, 30 Dec 2024 16:58:13 GMT</pubDate>
            <atom:updated>2024-12-30T16:58:13.028Z</atom:updated>
            <content:encoded><![CDATA[<p>Practical Guidelines for Enhanced Collaboration</p><h4>Objective</h4><p>Often, team development trainings tend to be esoteric in nature and difficult to translate into actionable insights or practical guidelines. The Five Dysfunctions of a Team provides a unique perspective on challenges that hurt a team’s ability to collaborate and be effective. This paper seeks to provide practical guidelines for incorporating the core principles of the Five Dysfunctions into a SCRUM team with the intent of developing a high-performing team that consistently delivers on its goals.</p><h4>Background</h4><h4>SCRUM</h4><p>SCRUM is an agile framework first developed by Jeff Sutherland and Ken Schwaber that focuses on helping teams “generate value through adaptive solutions for complex problems.” Its core theory is based on lean thinking and the observation that reducing waste and continuously learning from experience are essential. SCRUM has four foundational, interdependent concepts that enable a team to iteratively and incrementally generate value. These concepts, at a high level, are:</p><blockquote>1. Sprint: a 2–4-week time-boxed event where work is performed</blockquote><blockquote>2. Transparency: Process and work must be visible to all. Transparency allows for inspection.</blockquote><blockquote>3. Inspection: Work is to be inspected frequently to ensure adherence to goal and identification of defect. Inspection allows for adaptation.</blockquote><blockquote>4. Adaptation: Corrections should be made when deviations are detected.</blockquote><p>It is important to point out that a SCRUM team is expected to be self-organizing or self-managed without which adherence to these concepts cannot be realized.</p><p>Schwaber, K. and Sutherland, J. (2020)</p><h4>The Five Dysfunctions</h4><p>Patrick Lencioni identified five dysfunctions as set of challenges that teams routinely face and must address head-on to maximize its effectiveness and create a cohesive, high-performing team. These dysfunctions are interdependent and build upon each other creating a cascading effect where improvements in one dysfunction positively influences the others resulting in more effective and cohesive team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/324/1*W9bltUhmtn1meuSmc_MLPg.png" /><figcaption>The 5 Dysfunctions of a Team</figcaption></figure><p>Lencioni, P. M. (2002)</p><p>The rest of this paper will look at each of these dysfunctions from a SCRUM perspective to identify opportunities to incorporate them to enhance the overall effectiveness of a SCRUM team.</p><h3>Five dysfunctions addressed in a SCRUM team</h3><p>First, before diving into each dysfunction, I recommend that a team workshop is conducted outside of SCRUM events to collaboratively develop a team charter. The purpose of this workshop would be to discuss and agree on Core Values, Team Norms, Team Roles, Metrics of Success, Definition of Done and developing an Ownership mindset. This team charter can then be referenced at all stages of SCRUM. In my experience, it leads to increased awareness within the team on overall goals and expectations. Once the charter is developed, make it accessible - circulate it within the team via email or chat and share it on team site. You can further formalize it by requesting each member sign the document.</p><h4>1. <strong>Absence of Trust</strong></h4><p><strong>Strategy</strong>: Increase transparency and openness through diversified questioning in daily stand-ups, sprint reviews and retrospectives. During standups rotating the types of questions asked can reveal different perspectives and encourage honesty which helps develop trust between team members.</p><p><strong>Example</strong>: The standard set of questions in Daily Standup tend to be: “What did you do yesterday? What will you do today? Are there any impediments?”. We should consider exploring and testing different question sets. For example: “What challenges did you encounter? How did you overcome them? What can the team help with?” Diversifying questions can help deepen the understanding among team members about each other’s work and challenges.</p><h4>Fear of Conflict</h4><p><strong>Strategy</strong>: Promote constructive and respectful conflict by establishing clear communication norms and actively engaging SCRUM masters in facilitating discussions. Encourage team members to express differing opinions during sprint planning and retrospectives.</p><p><strong>Example Approach</strong>: Implement a “conflict rule” where team members are encouraged to express disagreements during working sessions, sprint reviews and retrospectives but must also offer alternative solutions or constructive feedback. This will help ensure that conflicts are productive and focused on improving outcomes.</p><h4>Lack of Commitment</h4><p><strong>Strategy</strong>: Clarify goals and roles within the team to ensure all members are aligned and committed. Use sprint planning to set clear, achievable goals and involve the team in decision-making to increase ownership and commitment.</p><p><strong>Example Implementation</strong>: During sprint planning, have each team member restate the sprint goals in their own words and describe their role in achieving these goals. This practice helps to ensure everyone understands and commits to the sprint objectives and their personal contributions. This would also be a good time to review the team charter especially if you see sprints not achieving their stated goals.</p><h4>Avoidance of Accountability:</h4><p><strong>Strategy</strong>: Foster a culture of mutual accountability by using daily standups to monitor progress and identify obstacles. Encourage team members to hold each other accountable through peer reviews and pair programming.</p><p><strong>Example Technique</strong>: Implement a peer review system where team members regularly assess each other’s work. This can be done informally during the sprint or more formally at the end, ensuring that everyone feels responsible for maintaining team standards and deadlines. Refer to the team charter to ensure all team members are aligned especially on the Definition of Done and Ownership mindset.</p><h4>Inattention to Results</h4><p><strong>Strategy</strong>: Keep the team focused on achieving results by setting specific, measurable goals for each sprint. Use metrics and KPIs to track progress and celebrate team achievements to maintain a results-oriented culture.</p><p><strong>Example</strong> <strong>Metrics</strong>: Introduce a dashboard that tracks key performance indicators like sprint velocity, backlog items completed, and quality metrics. Regularly review these metrics in sprint reviews and celebrate when goals are met or exceeded, thus reinforcing the team’s focus on results. You can bring this dashboard up during standups and ensure team members speak in context of the current state of the sprint. Again, if you see the team deviating from the goals, bring up the team charter for review and discussion.</p><h3>Conclusion</h3><p>Successfully navigating the landscape of SCRUM through the lens of the Five Dysfunctions offers a profound opportunity to transform a group of individuals into a synergistic team capable of surpassing its collective goals. It is vital for SCRUM teams to not only acknowledge these dysfunctions but to actively engage in overcoming them. Each step taken to address trust, conflict, commitment, accountability, and attention to results not only enhances project outcomes, but it also creates a highly efficient team that is more resilient against future challenges.</p><p>To truly capitalize on the potential of SCRUM, teams must commit to a continuous cycle of reflection and adaptation, incorporating lessons learned into their daily routines and strategic approaches. By systematically addressing each dysfunction, teams can create a robust framework for cooperation and innovation, ensuring that every sprint contributes not just to immediate project goals but to the sustained growth and effectiveness of the team itself.</p><p>Final note — be flexible, experiment with these approaches, tackle them one at a time. The path to high performance and high efficiency is an iterative and incremental process. Just as sprints build on one another to create a valuable product, they can also simultaneously address the five dysfunctions of a team in an iterative manner, leading to a more cohesive and high-performing team one sprint at a time.</p><p>Remember, if you don’t see the results, continue to iterate and calibrate. That is the true spirit of Agile/SCRUM.</p><h3>References</h3><p>Lencioni, P. M. (2002). The Five Dysfunctions of a Team: A leadership fable. <a href="http://ci.nii.ac.jp/ncid/BA5846175X">http://ci.nii.ac.jp/ncid/BA5846175X</a><br>Manifesto for Agile software development. (n.d.). <a href="https://agilemanifesto.org/">https://agilemanifesto.org/</a><br>Schwaber, K. and Sutherland, J. (2020) The Scrum Guide <a href="https://scrumguides.org/scrum-guide.html">https://scrumguides.org/scrum-guide.html</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1285adec7d4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>