Agile for Humans with Ryan Ripley and Todd Miller Agile for Humans, LLC

Pawel Mysliwiec, a fellow professional Scrum trainer with Scrum.org, joins host Ryan Ripley on the "Becoming a Scrum Master" podcast.

Pawel's Entry into Scrum: Pawel recounts his initial, unknowing encounter with Scrum while working as a product manager on bank credit transaction software. He participated in what he later learned were Scrum meetings, such as the daily Scrum, without realizing it was part of Scrum methodology.

Eureka Moment in Scrum: Pawel experienced his transformative moment with Scrum on a complex project within a waterfall program. He managed two teams and decided to apply Scrum internally while maintaining a project manager facade externally. This led to successful incremental deliveries and effective collaboration between business and IT personnel, which was a revelation to him.

Evolution of Scrum Master Role: Pawel reflects on the evolution of the Scrum Master role, emphasizing the shift from understanding and practicing Scrum to ensuring the team's long-term success and delivering financial value. He believes the role encompasses facilitating team effectiveness and reliability and helping teams become examples of good practice.

Advice for Aspiring Scrum Masters: Pawel advises patience and resilience as key traits for Scrum Masters. Change doesn't happen overnight, and a good Scrum Master should be resilient enough to keep trying while being patient for the change to occur. He also suggests a learning-by-doing approach and recommends reading books on Scrum Mastery, particularly for beginners.
🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

Magdalena discusses her transition from traditional project management to Scrum. In 2008, while experiencing project delays and rapid business environment changes, she discovered Scrum in a project management course, finding it a revelation for addressing these challenges.

Firlit highlights a pivotal moment in her journey: recognizing Scrum's ability to respond to market changes and customer needs, previously overlooked in traditional project management approaches. This realization initiated discussions about adopting new methodologies within her organization.

Her Scrum Master journey involved a professional transformation and a shift in personal mindset and habits. After a few years in various roles related to agile coaching and product management, she found passion and happiness in these new methodologies.

Firlit emphasizes the evolving role of a Scrum Master, stressing the importance of focusing on organizational aspects and value orientation rather than just team-level concerns and basic practices. She discusses challenges in organizational culture and the need for openness to change.

Lastly, she advises aspiring Scrum Masters to focus on the broader organizational context and product ownership, emphasizing the need to understand and respond to complexity, market changes, and technology advancements. She recommends thinking beyond team effectiveness and tool usage to include organizational agility and product outcomes.
🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

David shares his first exposure to Scrum in 2007 during a two-day training seminar organized by his then-employer. This led him and his colleagues to experiment with Scrum in their workplace, with David volunteering to be the Scrum Master.

Application and Evolution of Scrum Mastery: David discusses applying Scrum principles both in an academic setting and later as a product owner in a Toronto startup. He reflects on the evolution of his understanding of the Scrum Master role, emphasizing its complexity and the importance of having positional authority and experience in technology and business domains.

Insights on the Scrum Master Role: The conversation delves into the changing perceptions of the Scrum Master role, with both agreeing it's not an entry-level position but one requiring experience and authority. They note a trend where the role has been misunderstood and diminished, advocating for a return to viewing it as a leadership position.

Advice for Aspiring Scrum Masters and Resources: David advises new Scrum Masters to understand the agreements within their teams, focus on the concept of 'Definition of Done,' and foster relationships beyond work.

He recommends the book The Wisdom of Teams and shares his involvement in training and consulting and his book about the Phoenix payroll system failure in Canada's federal government.

🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

The video is part of a series in which hosts Todd Miller, and Ryan Ripley discuss common myths or facts about Scrum, encouraging viewers to participate by commenting on their opinions before watching the response.
🔍 Today's Myth or Fact: "The Scrum Master is responsible for the personal growth of the developers."
Todd and Ryan agree that the statement is a myth, emphasizing that personal growth and development are individual responsibilities, not the Scrum Master's.
🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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

Lavaneesh Gautam, a professional scrum trainer, shares his journey to becoming a Scrum Master on the "Becoming a Scrum Master" podcast with host Ryan Ripley.

Gautam first encountered Scrum while working as a developer/business analyst in a fintech company in 2011. He appreciated its transparency and visual management, which motivated him to become a Scrum Master in 2014.

His interest in Scrum was sparked by the limitations he observed in the waterfall method, particularly its command-and-control culture, which diminished job satisfaction.

Gautam highlights a pivotal experience in an automotive company where a project failure due to a lack of agile methodology made him realize the importance of iterative and incremental work and understanding the underlying needs behind requirements.

He advises aspiring Scrum Masters to continually learn and explore beyond formal training, emphasizing the importance of mindset, experimentation, and understanding broader aspects of product management and team dynamics.

🔔 Stay tuned for more episodes filled with expert knowledge and intriguing discussions. We encourage you to share your thoughts and questions in the comments below. Your input is valuable to our community, and we often feature your inquiries in our future videos!

👍 Found this episode enlightening? Please LIKE and SHARE it with your network to spread the knowledge!

🔗 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

🌐 Connect with Agile for Humans:

📘 Website - https://agileforhumans.com/


🐦 Twitter - https://twitter.com/agileforhumans


🔗 LinkedIn - https://www.linkedin.com/company/agile-for-humans-llc


🔍 The Evidence-Based Company - https://theevidencebasedcompany.com/


📧 Email - ryan@agileforhumans.com


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