As part of the Scrum.org webinar “Ask a Professional Scrum Trainer - Martin Hinshelwood - Answering Your Most Pressing Scrum Questions” I was asked a number of questions. Since not only was I on the spot and live, I thought that I should answer each question that was asked again here, as well as those questions I did not get to.
In case you missed it, here is the recording of yesterday’s Ask a Professional Scrum Trainer webinar with Martin Hinshelwood! Watch here: http://ow.ly/ijiM50vwEkD
[Question] How do you handle conflicts between 2 people when one of them is a disciplinarian, within an agile environment?
The accountability for conflict resolution within a team lies with that Development Team and with the following escalation:
- The Development Team is responsible for who is on the team and not
- The Scrum Master is responsible for the Development Team’s understanding and implementation of Scrum.
- The Scrum Master is responsible for solving impediments.
The first focus needs to be on the Development Team to solve the problem, the second on giving the Scrum Team the skills required to do that. I want to help the Scrum Team understand the issue with this behaviour and then have it discussed at the next Sprint Retrospective. During the next Sprint I might try to facilitate the Scrum events a little differently to provide some discussion points for the next Sprint Retrospective. I would likely want to focus on facilitation techniques that promote everyone getting a voice, like the 1-2-4-All Liberating Structure. During the Events, or any discussions that involve the overbearing personality, when they try to asserts themselves, change tac immediately to the 1-2-4-All. In 1-2-4-All there is 1 minute of silent reflection, followed by 2 minutes in pairs, then 4 minutes in pairs-of-pairs, then have each group share their best idea with everyone. This should have the effect of mitigating the loud voice, allowing everyone to be heard, and you can focus on coaching that person to listen. Its important for the Scrum Master to have some skills in Life Coaching, and Cognitive Therapy. These additional skills can help a great Scrum Master more effectively be a guide for the Scrum Team.
At the Sprint Retrospective you may want to use “Heard, Seen, Respected” to have each team member share share a time when they were not heard. This could facilitate a conversation, and may provoke reflection in loud individuals. Be careful that you dont end up with too much conflict!
The Third escalation is the one that we dont want to have to enact, go back and try again with the first and second!
If all else fails then the Scrum Master may need to intervene, or provide intervention through whatever corporate processes that you have. If the Team cant solve the problem, and you have failed to coach that person, you may need to bring in outside help. If you have an Agile friendly HR that is able to provide additional coaching that would be awesome. If HR understands the value of Team, and folks working well together they may have some additional ideas.
If after all of those avenues have been exhausted then maybe the Team Member is the impediment.
There is nothing wrong with not being a good fit for a team. A team is a group of people, and people don’t always get along and no matters how much you focus on professionalism; there are always individuals that should not be in the same circles. Maybe you need to look for a way to place that person elsewhere in an environment that more suits their personality.
While there are no right answers there are some answers that are better than others. For your given situation select the most right answer, and iteration to the best version of it.
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
Should the Scrum Master always remove impediments?
Explains when a Scrum Master should remove impediments, focusing on team self-sufficiency, true impediments, and supporting team growth …
What's the best way to work around multiple PO?
Guidance on addressing issues with multiple Product Owners in Scrum, highlighting the need for clear backlog ownership and accountability to …
What is your perspective on collocation?
Explores the benefits and challenges of collocation in Scrum teams, comparing face-to-face collaboration with remote work, and offering …
In Nexus with 5 Scrum teams, how can the Product Owner attend all Sprint Planning events?
Explains how a Product Owner can manage Sprint Planning across multiple Scrum teams in Nexus by delegating, using area or team owners, and …
How do you incorporate a Design Sprint in Scrum?
Explains how to integrate Design Sprint activities within Scrum by embedding design and UX work into regular sprints and backlog refinement, …
Navigating Team Conflict: How Scrum Masters Can Prevent 'War' in Agile Projects
Explores how Scrum Masters can identify, manage, and prevent destructive team conflict in Agile projects, promoting healthy collaboration …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
The Definition of Done is a Commitment to Quality
Defines the Definition of Done in Scrum as a clear, shared standard for quality, ensuring increments are releasable, transparent, and …
Why Your Definition of “Done” Is Holding Back Quality, Agility, and Trust, And How to Raise the Bar
Is your team’s “done” really done? Discover how a clear, objective definition of done boosts quality, agility, and trust in product …
Acceptance Criteria vs Definition of Done: Why Getting This Right Builds Trust and Delivers Quality Faster
Stop confusing acceptance criteria with definition of done, learn the crucial difference to boost quality, speed, and trust in your agile …
How to Evolve Your Definition of Done: Start Small, Grow Smarter, and Build Lasting Momentum
Unlock a smarter Definition of Done, start small, evolve standards, and build team momentum without overwhelm. Discover how progress drives …
Why Most Transformations Fail Without Honest Conversations
Most transformations fail without open, honest conversations that address real issues, making transparency and tough dialogue essential for …
Why Your Definition of Done Is the Secret Weapon for Real Business Impact and Agile Growth
Transform your definition of done into a strategic advantage, deliver real value, reduce risk, and drive business impact with every sprint.
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
Futureproof Leadership: How CTOs Can Cut Through the Noise and Lead with Clarity, Confidence, and Culture
Struggling with tech change? Discover how clarity, evidence, and culture can futureproof your team, no chasing trends, just smart …
From Burnout to Breakthrough: How CTOs Can Lead with Clarity, Resilience, and Real Innovation
Feeling overwhelmed as a tech leader? Discover how to shift from chaos to clarity and build resilient, future-ready teams, without burning …
Human and AI Agency in Adaptive Systems: Strategy Before Optimisation
Explores the distinct roles of human and AI agency in adaptive systems, emphasising human-led strategy and accountability versus AI-driven …
Stop Chasing Trends: How Real Agility and DevOps Build Resilient, Adaptable Teams
Stop chasing trends, build real agility. Discover how DevOps and agile create resilient teams, smoother delivery, and sustainable …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Big Bang Rewrites Fail: How Sustainable Change and Engineering Excellence Transform Legacy Systems
Ditch the Big Bang rewrite. Discover why sustainable, in-place change drives true engineering excellence and lasting transformation in your …
Is Agile Really Just a Mindset?
Explores Agile as a disciplined system of delivery, emphasizing engineering excellence, CI/CD, observability, and system design over mindset …
Telling People What to Do Is Not Leadership. It’s a Failure of System Design
Explores why real leadership means designing systems that enable team autonomy, flow, and accountability, rather than relying on …
From Legacy Pain to Modern DevOps: My Proven Roadmap for Real Engineering Transformation
Transform legacy engineering with a proven, step-by-step approach, learn how to automate, adapt, and build a resilient, modern DevOps …