Agile for Humans with Ryan Ripley and Todd Miller

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

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive. The seventh statement from Ken: "The use of Scrum to become an optimized product development and management organization is a change process that must be led from the top and requires change by everyone within the enterprise. Change is extremely difficult and fraught with conflict, and may take many years of sustained effort. Turnover of staff and management can be expected." 🎥 Video Description: Welcome back to our transformative "Scrum is Hard and Disruptive" series! In this installment, we delve into the heart of Scrum mastery with "The Point of Scrum is DONE." Join us as we explore the demanding yet rewarding journey of implementing Scrum in product development and management. This episode is a must-watch for anyone looking to excel in Scrum practices and achieve exceptional results. Key Takeaways from This Episode: 🛠️ Engineering Excellence: Discover how Scrum's rigorous standards elevate engineering practices. We delve deep into the importance of adhering to the "Definition of Done," fostering a culture of technical excellence and precision. 🔄 Iterative Improvement: Learn about the iterative nature of Scrum. This episode highlights how Scrum pushes teams to continuously enhance their skills and optimize the value delivered in each sprint. 🎯 Dual Focus: We emphasize the critical balance between honing technical skills and effective product management. Understand how this synergy ensures both quality output and maximized return on investment. 🌉 Bridging Effectiveness Gaps: Gain insights into the pivotal role of Scrum Masters in narrowing the divide between current practices and desired outcomes. We discuss strategies to mitigate risks and overcome potential incompetencies in teams. 🚀 Embracing Challenges: Be inspired to adopt a mindset of relentless improvement and face complacency head-on. This episode is a call to action for all Scrum practitioners to embrace the challenges and thrive in the Scrum environment. 👉 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 sixth statement from Ken: "The iterative, incremental nature of Scrum puts stress on the product development organization to improve its engineering skills and on the product management organization to optimize the return on investment of every release and project. The phrase, “That can’t be done here” really means that it will be very difficult to do so. The gap between current practices and target practices is a measure of incompetence and competitive risk." 🚀 Video Summary: Explore the demanding journey of Scrum mastery! 🌟 This installment of the "Scrum is Hard and Disruptive" series, titled "The point of Scrum is DONE," delves into the rigorous demands Scrum places on product development and management teams, emphasizing the need for exceptional engineering skills and ROI optimization. Key Takeaways: 🛠️ Engineering Excellence: Scrum demands advanced engineering practices and a strong commitment to the "Definition of Done," fostering technical prowess. 🔄 Iterative Improvement: Highlights the iterative nature of Scrum, pushing teams towards constant skill enhancement and value optimization. 🎯 Dual Focus: Stresses the importance of balancing technical skill development with product management, ensuring quality and maximized ROI. 🌉 Bridging Effectiveness Gaps: The video underscores the Scrum Master's role in closing the gap between current and target practices, mitigating risks and incompetence. 🚀 Embracing Challenges: Encourages a mindset of continuous improvement and confronting complacency, crucial for Scrum's success. 👉 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 fifth statement from Ken: "Whenever an enterprise modifies or only partially implements Scrum, it is hiding or obscuring one or more dysfunctionalities that restrict its competence in product development and management." 🚀 Video Summary: Dive into the intricate world of Scrum implementation! 🌟 This video unpacks the challenges and misconceptions associated with Scrum in enterprises, focusing on how partial or incorrect practices can hide underlying issues in product development and management. 💡 Key Takeaways: 🛠️ Framework vs. Solution: Scrum is a framework, not a fix-all solution, highlighting areas for improvement in product development. 🚫 Common Missteps: Watch out for "Sprint zero" and other misconceptions misaligning with true Scrum principles. 🧭 Role of Scrum Master: Emphasizes the critical, senior role of Scrum Masters in steering successful Scrum implementation. 🗣️ Engage with Developers: Direct engagement with developers is key to uncovering and addressing implementation challenges. 📈 Continuous Improvement: Scrum provides continuous opportunities to inspect, adapt, and make better decisions. 👉 Stay tuned for more from our "Scrum is Hard and Disruptive" series as we dive into all 15 key statements of Scrum's transformative approach. 💬 Let us know your thoughts in the comments and don't forget to like and subscribe for more insights and updates. 🔔 🔗 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 fourth statement from Ken: "An enterprise can use Scrum as a tool to become the best product development and management organization in its market. Scrum will highlight every deficiency and impediment that the enterprise has so the enterprise can fix them and change into such an organization." 🔍 In this episode, we delve into the transformative power of Scrum! Join us as we explore how it's more than just a project management tool; it's a key to product development and management excellence. 🛠️ Key Takeaways: 🌟 Scrum for Excellence: Discover how Scrum can elevate your enterprise to the pinnacle of your market. 🧐 Identifying Weaknesses: Learn how Scrum's unique approach to highlighting organizational deficiencies can be a game-changer. 💡 Embracing Change: Understand the importance of adaptation and proactive problem-solving with Scrum. 🚧 Overcoming Adaptation Challenges: We discuss the common hurdles organizations face in adapting and how to overcome them. 🏆 Success Path with Scrum: Find out how embracing Scrum's insights can lead your organization to the top. 👉 Stay tuned for more from our "Scrum is Hard and Disruptive" series as we dive into all 15 key statements of Scrum's transformative approach. 💬 Let us know your thoughts in the comments and don't forget to like and subscribe for more insights and updates. 🔔 🔗 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 post written by Ken Schwaber in 2006 that covers 15 ways Scrum is both hard and disruptive. The third statement from Ken: 3. If waterfall suits current needs, continue using it. 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 post written by Ken Schwaber in 2006 that covers 15 ways Scrum is both hard and disruptive. The second statement from Ken: 2. Scrum is optimized for high yield product management and product development. Scrum is particularly appropriate for high risk, complex, large projects and can be used when other parts of the endeavor are hardware or even waterfall development. 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 post written by Ken Schwaber in 2006 that covers 15 ways Scrum is both hard and disruptive. The first statement from Ken: 1. Scrum is a framework for iterative, incremental development using cross-functional, self-managing teams. It is built on industry best practices, lean thinking, and empirical process control. Here is the original white paper: https://www.verheulconsultants.nl/ScrumIsHardandDisruptive.pdf Join this channel to get access to the perks and exclusive videos: https://www.youtube.com/channel/UCZYWqpkc-YzAndAt90arxTA/join 🔗 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 us for an exciting episode of "Becoming a Scrum Master"! Today, we have the privilege of hosting Nichervan Fazel, an influential figure in the Scrum community. Host Ryan Ripley engages Nichervan in a thought-provoking discussion about his Scrum journey. From an early setback in product development to becoming a dedicated Scrum Master, Nichervan shares invaluable insights and experiences. 👉 Don’t forget to LIKE, SUBSCRIBE, and hit the NOTIFICATION BELL to keep up with our inspiring series! 📜 In this Episode: 00:00 - Introduction to Nichervan Fazel 04:20 - Nichervan’s First Encounter with Scrum 08:15 - The Turning Point Towards Embracing Scrum 12:30 - Nichervan’s Defining Moment with Scrum in Product Development 17:45 - Nichervan’s Growth and Transformation in the Scrum Master Role 23:10 - Key Advice and Perspectives for Aspiring Scrum Masters 🌟 Key Takeaways: Discover Nichervan Fazel’s path to mastering Scrum and its profound effect on his career trajectory. Learn about the critical challenge that nudged him towards Scrum methodologies. Explore a pivotal project where Scrum proved its efficacy in a complex business environment. Understand how Nichervan’s perception and approach to the Scrum Master role evolved with experience. Gain essential tips and insights for those aiming to thrive as Scrum Masters. 💡 A Must-Watch for Scrum Aficionados: Whether you’re new to Scrum or a seasoned expert, this episode is a wellspring of wisdom. Nichervan Fazel’s journey and advice offer a distinct, hands-on perspective on effectively adopting and excelling in the Scrum framework. 🔔 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

🌟 SUMMER SLAM 2024 with AGILE FOR HUMANS! 🌟 We teach 10 public courses from April 1 to August 31st, and you can attend them all for a one-time payment of $2500. Grab your pass today and spend this summer leveling up with Ryan and Todd. 🚀 Today, we are thrilled to have Will Seele, a distinguished personality in the Scrum arena, join host Ryan Ripley for an enlightening discussion on his Scrum mastery journey. From his initial encounter with Scrum at Hewlett Packard to evolving into a seasoned Scrum Master, Will shares invaluable insights and experiences. 👉 Don't forget to LIKE, SUBSCRIBE, and hit the NOTIFICATION BELL for the latest episodes in this insightful series! 📜 In this Episode: 00:00 - Introduction of Will Seele 03:45 - Will's First Exposure to Scrum at Hewlett Packard 07:10 - The Challenge of Managing a Networked Supercomputer Project 11:25 - The Eureka Moment in Scrum from University to Professional Life 16:50 - How Will's Perception of the Scrum Master Role Has Evolved 21:30 - Key Advice and Takeaways for Aspiring Scrum Masters 🌟 What You'll Discover: This book explores Will Seele's fascinating journey into the realm of Scrum and its influence on his career trajectory. It also discusses the formative challenge that honed his skills in Scrum methodologies, how an early project in university unknowingly sowed the seeds of Scrum's potential and the evolution of Will's approach and understanding of the Scrum Master role over time. Finally, it provides crucial advice and actionable tips for budding Scrum Masters. 💡 A Must-Watch for Scrum Enthusiasts: This episode is a gold mine for anyone passionate about Scrum, from novices to veterans. Will Seele's path and wisdom offer an authentic and practical viewpoint on mastering the Scrum framework effectively. Stay tuned for these expert insights! 🔔 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 discuss the uncertain and complex nature of recent layoffs, particularly in the tech industry, attributing them to various global events. Emphasizing a pragmatic approach to employment, they advise viewing the employer-employee relationship as a transactional exchange of time and talent for compensation. Todd and Ryan underscored the importance of continuous personal and professional development through various means like reading, networking, and utilizing online resources. Drawing from personal experiences, they highlight the resilience of skill enhancement, especially during layoffs. They conclude with a call to focus on what one can control, advocating for a realistic and informed approach to career planning and economic changes while maintaining a cautiously optimistic outlook. Join the Evidence-Based Management interactive two-day course here: https://bit.ly/eblcourse 🔗 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 the Evidence-Based Management interactive two-day course here: https://bit.ly/eblcourse 🔗 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 the Evidence-Based Management interactive two-day course here: https://bit.ly/eblcourse 🔗 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 the Evidence-Based Management interactive two-day course here: https://bit.ly/eblcourse 🔗 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