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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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