DiscoverAgile for Humans with Ryan Ripley and Todd MillerScrum is Hard and Disruptive 14 - Conflict Not Fights
Scrum is Hard and Disruptive 14 - Conflict Not Fights

Scrum is Hard and Disruptive 14 - Conflict Not Fights

Update: 2024-05-07
Share

Description

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive.


The fourteenth statement from Ken:


"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."


Natural Conflict in Teams: The episode discusses how conflict is a natural occurrence in teams, especially under pressure. This pressure can be constructive and lead to better performance if it's oriented towards clear goals, such as achieving Sprint and product goals in Scrum.


Healthy vs. Unhealthy Conflict: They emphasize the difference between healthy and unhealthy conflict. Healthy conflict focuses on problem-solving and can be beneficial, while unhealthy conflict, which can escalate to personal fights, is detrimental. The key is to maintain focus on solving problems, not winning arguments.


Role of Scrum Values in Managing Conflict: Scrum values like commitment are highlighted in managing conflict. These values support positive, natural conflict oriented towards team goals and problem-solving instead of destructive fights.


Team Dynamics and Conflict Resolution: The hosts discuss the importance of recognizing when a discussion is veering away from productive conflict and turning into a personal fight. They stress the importance of team members being able to intervene, reset the focus on the problem, and avoid stubbornness in pursuit of being right.


Balance Between Agreement and Conflict: They conclude that while conflict is necessary for progress, it needs to be balanced. Neither constant agreement nor continuous fighting is beneficial. A good Scrum Master, product owner, or team member should help maintain this balance, encouraging healthy conflict while preventing fights.


πŸ‘‰ Follow our journey through all 15 insights in Ken Schwaber's white paper, revealing the enduring relevance of Scrum principles.


πŸ’¬ Share your perspectives in the comments and remember to like and subscribe for more in-depth Scrum discussions. πŸ””


πŸ”— Here is the original white paper: https://www.verheulconsultants.nl/ScrumIsHardandDisruptive.pdf


ο»ΏπŸ”— Join Ryan & Todd's Scrum.org course: https://buytickets.at/agileforhumansllc

Explore more:

πŸ“– "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

βœ… Subscribe to this channel for Agile, Scrum, and Kanban insights: https://www.youtube.com/agileforhumans?sub_confirmation=1


Learn more about your ad choices. Visit megaphone.fm/adchoices

CommentsΒ 
In Channel
loading
00:00
00:00
x

0.5x

0.8x

1.0x

1.25x

1.5x

2.0x

3.0x

Sleep Timer

Off

End of Episode

5 Minutes

10 Minutes

15 Minutes

30 Minutes

45 Minutes

60 Minutes

120 Minutes

Scrum is Hard and Disruptive 14 - Conflict Not Fights

Scrum is Hard and Disruptive 14 - Conflict Not Fights

Agile for Humans, LLC