In the latest episode of "Scrum is Hard and Disruptive," Todd Miller and Ryan Ripley dive deep into a topic every Scrum team faces but rarely addresses openly: conflict. Contrary to popular belief, conflict isn’t the enemy of progress—it’s a natural and essential part of team dynamics, especially when working under pressure to achieve challenging goals.
Ken's 14th Statement: "A team consists of people under pressure to do their best. Conflict is natural and the team needs to know how to deal with the conflict and have resources to draw on when needed."
Pressure: A Catalyst for Great Work
Todd opens the discussion by reflecting on his career, admitting that some of his best work has come from moments of intense pressure. In Scrum, the pressure to achieve Sprint and product goals is unavoidable, and when channeled correctly, it can drive focus and creativity. However, it’s crucial that this pressure remains healthy, motivating the team rather than overwhelming them.
Understanding the Levels of Conflict
Conflict is not inherently negative; it only becomes problematic when it escalates beyond constructive debate. Ryan introduces the concept of conflict levels, ranging from problem-focused discussions to personal disagreements and full-blown battles where winning overtakes solving the problem. The key is to recognize when conflict stops being about the work and starts being about ego.
Commitment: The Unsung Hero of Scrum Values
Commitment is not just about showing up—it’s about engaging in the kind of healthy, respectful conflict that moves the team forward. Todd and Ryan stress the importance of staying focused on the problem rather than letting conflicts turn into personal fights. It’s this commitment to the team and the goal that keeps conflicts productive and avoids the pitfalls of toxic disagreements.
Balancing Conflict and Agreement
A balanced team dynamic is not about constant harmony or endless debates. Great teams know when to argue passionately for their ideas and when to call a timeout to reset. Scrum Masters, Product Owners, and Developers all play a role in maintaining this balance, ensuring that the team's energy remains directed toward solving problems, not settling personal scores.
The Bottom Line: Conflict Fuels Progress
Conflict, when managed correctly, is not something to shy away from—it’s a powerful force that propels self-managing teams forward. The next time your Scrum team feels the heat, remember: it’s not about avoiding conflict; it’s about embracing it as a tool for growth and innovation. Stay committed to the problem, keep conflicts healthy, and watch your team thrive.
Be sure to check out the full episode and stay tuned for the final installment of this insightful series!
⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc
Check out their books:
📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- https://amzn.to/4690qJy
📖 "Fixing Your Scrum: Practical Solutions to Common Scrum Problems" on Amazon -- https://amzn.to/46dAQTC