Agile for Humans with Ryan Ripley and Todd Miller

Welcome to a new enlightening episode of "Becoming a Scrum Master"! In this episode, we're excited to feature Souleymane Thiongane, a remarkable figure in the Scrum community, as he joins host Ryan Ripley for an engaging conversation about his journey with Scrum. From his initial discovery of Scrum as a software developer to becoming a passionate advocate and master of the Scrum framework, Souleymane shares valuable lessons and experiences. 🔗 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

Jowen Mei's scrum journey began in 2010 as a C# developer in Microsoft technology. His first experience with Scrum was transformative, sparking his love for the framework due to its focus on autonomy, mastery, and purpose, such as team collaboration, TDD, and direct customer engagement. After his initial scrum experience, Mei launched his own agile-focused startup, which faced initial challenges. He returned to consultancy, gradually shifting from development to scrum mastering, influenced by the role's complexity and its impact on professional and personal life. Mei's early scrum master approach focused on strict adherence to practices and persuasion, but he evolved to emphasize coaching, inspiration, and empowering team ownership for sustainable improvement. For aspiring scrum masters, Mei emphasizes the importance of curiosity, humility, and an experimental mindset. He believes in understanding underlying reasons for team behaviors and adopting a continuous improvement mindset. Mei recommends Christopher Avery's book The Responsibility Process for scrum masters. He values its insights into the psychological aspects of ownership and responsibility and shares his appreciation for the book's impact on his understanding of team dynamics and leadership. 🔗 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

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

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive. The thirteenth statement from Ken: "Self-managing teams are extremely productive. When they work closely with the customer to derive the best solution to a need, they and the customer are even more productive." Self-Managing Teams' Productivity: The episode emphasizes that self-managing teams are highly productive, especially when they work closely with customers to find the best solutions. This collaboration enhances productivity for both the team and the customer. Autonomy and Team Ownership: The discussion highlights the benefits of autonomy in team settings. Teams that own their work without constant oversight tend to produce higher-quality results. This autonomy is linked to increased productivity and satisfaction. Resistance to Coercion in Workplaces: Current trends show resistance to coercive work environments, where employees are forced into specific work arrangements. Organizations enforcing strict mandates often face challenges like talent loss, emphasizing the need for trusting professional teams to self-organize and manage their work. Customer Inclusion and Empathy: It is vital to include customers in the development process. Direct interaction between teams and customers fosters empathy and a deeper understanding of real customer needs, leading to more effective solutions. Skill Development for Teamwork: The episode underscores the importance of developing teamwork skills. Teams need to learn how to self-manage effectively. While this isn't an inherent skill for everyone, with the right coaching and environment, teams can achieve high levels of productivity and impact. 👉 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

Coming from a development background, John Riley first encountered scrum around 2004, initially attracted to it due to its focus on agility and better project outcomes. Despite an early failure in an agile transformation attempt due to limited understanding and lack of support, he remained interested in Scrum. Shift to Scrum Master Role: Riley's profound engagement with Scrum began in 2010 while working on a banking application. Impressed by the effectiveness of a scrum environment and inspired by the scrum master of his team, he decided to pursue the scrum master role himself, taking over after the departure of the original scrum master. Eureka Moment and Evolution in Approach: Riley's approach to scrum evolved significantly after a candid conversation with team members who felt he was too rigid in his methods. This led to his realization that scrum is a flexible framework rather than a strict set of rules, prompting him to adopt a more observational and indirect coaching style. Advice for Aspiring Scrum Masters: He emphasizes the importance of finding a mentor for guidance and challenges, advocating for a mindset open to learning and adapting. Riley also suggests pairing up with someone experienced to better understand the agile and scrum mindsets. Book Recommendation and Conclusion: Riley recommends "Drive" by Daniel Pink as a crucial read for scrum masters, highlighting its insights into leadership and motivation. He underscores the importance of intrinsic motivation in the scrum master role. 🔗 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

Todd Miller, Will Seele, and Ryan Ripley discuss Agile's internal (organizational) focus and the gap left by not addressing the Value component of Product Management and delivery. In this Episode: Internal Focus of Agile: The discussion, led by Todd Miller and Ryan Ripley, challenges the common perception of Agile as customer-centric and value-oriented, proposing instead that Agile is predominantly focused on internal processes and organizational matters rather than directly benefiting customers. Agile Manifesto Analysis: The Agile Manifesto and its principles, when examined, emphasize team interactions, working software, and adapting to change but lack explicit directives that prioritize customer value or tangible benefits for the customer. Evolution and Additions to Agile: Over time, various frameworks like Scrum, XP, Kanban, and others have evolved under the umbrella of Agile, incorporating aspects like customer centricity and iterative development. However, these are seen as additions to the core Agile philosophy, which remains internally focused. Evidence-Based Management Connection: The conversation transitions to evidence-based management and its potential integration with Agile. This approach aims to complement Agile by introducing a more outward, value-driven focus, assessing Agile’s impact on customers and market performance. Insufficiency of Agile Alone: The presenters conclude that while Agile methodologies are crucial, they are insufficient to ensure organizational success. They stress the need to balance Agile's internal process focus and external value delivery, advocating for a continuous evaluation of Agile's effectiveness and alignment with strategic goals. 🔗 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

Andrii Glushchenko shares his unconventional journey into Scrum mastery. Glushchenko became a Scrum Master at 20 while working in an outsourcing company during the 2014-2015 Ukraine war. Initially a recruiter, his interest in Scrum was piqued by parallels he drew between the Scrum Master role and his basketball point guard experience. Challenges of Starting Without Knowledge: Glushchenko candidly admits that starting as a Scrum Master without proper knowledge was not ideal, as it led to wasting company resources while he learned on the job. He emphasizes that this approach is not recommended and underscores the importance of having a technical background and understanding of Scrum principles. Evolution of Understanding and Practice: Over time, Glushchenko's perception and execution of the Scrum Master role evolved significantly. He initially thought the role was limited to ensuring Scrum works at the team level. Still, he later realized it encompasses helping the entire company achieve its goals through Scrum implementation, involving change and operational management. Continuous Learning and Impact-Driven Approach: He highlights the necessity of constant learning, celebrating small victories, and being impact-driven. Glushchenko shares how he approaches problems by assessing the cost of fixing them against the potential gain, focusing on impactful changes. Advice for Aspiring Scrum Masters and Further Insights: Glushchenko advises aspiring Scrum Masters to understand the accountability and dedication required for the role. He recommends being diligent and constantly improving oneself. He also stresses the importance of supporting Ukraine in its current crisis, linking his personal background to broader global issues. 🔗 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

🔗 Join Ryan & Todd's Scrum.org course: https://buytickets.at/agileforhumansllc Becky Savill's journey to becoming a Scrum Master began nearly 10 years ago when, after six months of programming, her boss suggested she might be better suited to the role, despite her lack of prior knowledge about Scrum. Her boss recognized her passion lay not in coding but in solving team problems and working effectively together, leading her to dive deep into Scrum Mastering. A pivotal moment in Savill's career was during a Sprint retrospective, where a team member questioned the purpose of the meeting. The team's response, highlighting the positive changes and improvements made through Scrum, solidified her belief in Scrum's effectiveness. Over the years, Savill's understanding of being a Scrum Master evolved from focusing on the mechanics of Scrum to understanding its deeper purpose and ensuring it becomes a sustainable practice within teams. Savill emphasizes the importance of continuous learning and practical application in the Scrum Master role, advising aspiring Scrum Masters to engage actively in their professional development beyond just consuming knowledge. 🔔 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! 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 twelfth statement from Ken: "Managing a release or project to deliver only the highest value functionality and not deliver the rest optimizes value [and] is the job of product management and customers." The 12th episode of "Scrum is Hard and Disruptive" discusses the importance of delivering only high-value functionality in project management, emphasizing the role of product management and customer input. The hosts, Todd and Ryan, stress the need for product owners to say "no" to unnecessary features, highlighting the importance of avoiding waste and focusing on what's truly needed. They discuss using Evidence-Based Management (EBM) to validate the usefulness of features in production and advocate for objective decision-making in product development. The episode touches on the customer's responsibility in the development process, encouraging their involvement and accountability in deciding the essential features. The conversation also covers the importance of being ruthless in backlog management, akin to Steve Jobs with the iPhone, and the value of saying "not yet" to lower-priority items to maximize return on investment. 👉 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

🔗 Join Ryan & Todd's Scrum.org training courses: https://buytickets.at/agileforhumansllc Jenny Tarwater shares her journey into Scrum during an episode of "Becoming a Scrum Master" hosted by Ryan Ripley. She recalls her initial struggles at a large telecommunication company, where her early approach nearly led to her dismissal. Discovering a book on Scrum and Agile, she began applying these methodologies, transforming chaos into order with seven teams and exceeding stakeholder expectations within three sprints. Tarwater emphasizes the importance of collaboration and listening. She recounts a pivotal moment in a coaching class when she learned the value of not just being an expert but also understanding the perspectives of those within the organization. This experience shaped her approach to Scrum, highlighting the necessity of teamwork and context. Her perspective on the Scrum Master role evolved over time, and she stressed that there is no one-size-fits-all approach. Different organizations have varying needs, such as predictability, innovation, or quality, which require tailored approaches. She notes the challenge of adapting to other organizational structures and understanding each organization's problems. Tarwater advises aspiring Scrum Masters to prioritize continual learning and listening. She emphasizes the ever-evolving nature of knowledge in the field, suggesting that one should never stop learning and adapting. She recommends two books: "The Five Dysfunctions of a Team" for its insights into team dynamics and another unnamed but highly recommended book for Scrum Masters. 🔔 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

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive. The eleventh statement from Ken: "Iterative, incremental development is much harder than waterfall development; everything that was hard in waterfall engineering practices now has to be done every iteration, which is incredibly hard. It is not impossible, but has to be worked toward over time." Iterative and incremental development in Scrum is more challenging than traditional waterfall development, requiring constant attention to engineering practices and frequent iterations. Extensive upfront design and architecture planning in waterfall development is believed to reduce future risks. However, software development often leads to outdated designs as customer needs and market conditions change over time. Scrum emphasizes quick decision-making on basic architecture, like frameworks and databases, while building the product incrementally. It demands disciplined, professional attention to ongoing architectural and design decisions in response to evolving customer demands. The Scrum approach challenges traditional development models like waterfall, where work often expands to fill the allotted time, leading to over-engineered solutions. Scrum requires a shift in mindset, focusing more on doing and building features rather than extensive planning and discussion. Adopting Scrum effectively requires gradual, sustained effort to improve engineering practices and architecture. Teams and organizations need to develop this skill set over time, including a solid understanding of their definition of "done" to reflect the maturity of their Scrum implementation. 👉 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

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive. The tenth statement from Ken: "Scrum is not a methodology that needs enhancing. That is how we got into trouble in the first place, thinking that the problem was not having a perfect methodology. Effort centers on the changes in the enterprise that is needed." Scrum's Nature and Misunderstandings: The discussion emphasizes that Scrum is not a methodology needing enhancement, as attempting to perfect it led to initial troubles. It’s highlighted that Scrum is a framework, not a methodology, and should not be altered excessively. Scrum's Simplicity and Accessibility: When Compared to more complex methodologies and frameworks, Scrum’s guide is concise (13 pages), making it easily understandable without the need for extensive training, unlike more elaborate methods that require significant learning and interpretation. Adaptability and Contextual Use of Scrum: The speakers discuss the importance of adapting Scrum practices based on specific team and project contexts. They share personal experiences where certain practices were effective in one situation but not in another, illustrating Scrum’s flexibility and the need for situational awareness. Evolution of the Scrum Framework: The evolution of Scrum is discussed, noting that over time, the framework has become more streamlined, with a focus on removing unnecessary elements rather than adding new ones. This evolution aims to prevent dogmatic adherence to processes and encourage teams to focus on the intent of each Scrum event. Focus on Organizational Change Over Scrum Modification: The conversation shifts to the idea that efforts should be directed toward changing organizational structures and practices that hinder agility, rather than trying to improve Scrum itself. Emphasis is placed on overcoming organizational impediments to enhance the delivery of value to customers and gain competitive advantages. 👉 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

📖 "Unlocking Business Agility with Evidence-Based Management: Satisfy Customers and Improve Organizational Effectiveness" on Amazon -- https://amzn.to/4690qJy Ryan and Todd, along with Patricia Kong and Kurt Bidner, released a new book, "Unlocking Business Agility with Evidence-Based Management" (EBM), on October 31st. This book encapsulates over 10 years of their combined experience in EBM. The book, which spans eight chapters and is 166 pages long, covers EBM at various levels, including portfolio, project, and organizational levels. It aims to provide new theories and novel ideas about what EBM can offer organizations. The authors expressed their enthusiasm for the book's physical publication and discussed how it incorporates numerous real-life stories and experiences. They aim to clarify misconceptions about EBM and further its application in the business world. Ryan and Todd reflected on the unique aspects of writing this book compared to their previous work, "Fixing Your Scrum." They highlighted that "Unlocking Business Agility with EBM" offers fresh insights and elaborations on EBM rather than following an established path. The book is available in both eBook and paperback formats. The authors encourage readers to check it out, leave reviews, and share their thoughts. They also invite discussions and questions about EBM, intending to continue creating content and engaging with the community. 🔗 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 ninth statement from Ken: "The focus of using Scrum is the change from old habits to new ways of doing business. Scrum is not implemented or rolled-out as a process; it is used to foment change. " Podcast Focus: The podcast "Scrum is Hard and Disruptive" by professional scrum trainers Todd Miller and Ryan Ripley explores a white paper published by Ken Schwaber, co-creator of Scrum, in 2006. They assess 15 statements about Scrum to see if they remain relevant 17 years later. Scrum's Purpose: The primary focus of Scrum is to facilitate a transition from old habits to new ways of conducting business. It is emphasized that Scrum should not just be implemented as a new process but should be used to instigate significant organizational change. Common Misconceptions: There's a critique of how many organizations misunderstand Scrum, often using it merely as a new process rather than a tool for real change. This leads to maintaining old habits instead of adopting genuinely new ways of doing business. Technology and Business Integration: A key point discussed is the need to stop viewing IT departments as separate from the rest of the business. In the modern world, where technology is central, IT should be integrated into the core business processes. Challenges of Implementing Scrum: The podcast underscores that implementing Scrum can be challenging and disruptive, as it requires significant changes in organizational behavior and mindset. The goal is to move beyond superficial adoption of Scrum as a process to deeply ingrained changes in how businesses operate. 👉 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

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive. The eight statement from Ken: "The most serious impediments to using Scrum are habits of waterfall, predictive thinking over the last twenty to thirty years; these have spawned command and control management, belief that demanding something will make it happen, and the willingness of development to cut quality to meet dates. These are inbred habits that we aren’t even aware of anymore." 🚀 Video Summary: "The Point of Scrum is DONE" Dive into the challenging yet rewarding path of mastering Scrum with this enlightening episode from the "Scrum is Hard and Disruptive" series. This video focuses on the intense requirements that Scrum places on both product development and management teams, underlining the necessity of top-notch engineering skills and the pursuit of maximizing return on investment (ROI). Key Takeaways: 🛠️ Engineering Excellence: The video emphasizes that Scrum requires advanced engineering practices. It underscores the importance of adhering to a stringent "Definition of Done," which is pivotal in cultivating superior technical abilities within teams. 🔄 Iterative Improvement: The iterative nature of Scrum is a central theme, with the video highlighting how this approach propels teams towards ongoing enhancement of their skills and constant refinement of the value they deliver. 🎯 Dual Focus: A critical aspect discussed is the need to maintain a dual focus: developing technical expertise while simultaneously managing the product effectively. This balance is key in ensuring high-quality outcomes and optimizing ROI. 🌉 Bridging Effectiveness Gaps: The role of the Scrum Master is showcased as vital in bridging the gaps between current practices and desired outcomes. They play a crucial role in mitigating risks and addressing any incompetencies within the team. 🚀 Embracing Challenges: The video encourages teams to adopt a mindset geared towards continuous improvement and overcoming complacency. This approach is highlighted as essential for realizing the full potential and success of Scrum methodologies. 👉 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