Agile for Humans with Ryan Ripley and Todd Miller

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

Ryan and Todd look back at a 2006 post by Ken Schwaber, which covers 15 ways Scrum is both hard and disruptive. The fifteenth statement from Ken: "The role of enterprise management changes from telling people what to do to leading and helping everyone do their best to achieve goals. People aren’t resources, and managers aren’t bosses." Leadership Transition: In a Scrum environment, the role of ent...

Welcome to another exciting episode of "Becoming a Scrum Master"! In this episode, host Ryan Ripley is joined by the renowned Esther Derby, a pivotal figure in the agile community and author of "Seven Rules for Positive, Productive Change" and the upcoming second edition of "Agile Retrospectives". Join us as Esther shares her rich journey in the world of Scrum and Agile methodologies. 🔗 Join Rya...

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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