The final episode of "Scrum is Hard and Disruptive" emphasizes the essential shift in leadership from command-and-control to coaching and supporting teams. Effective Scrum leaders focus on setting meaningful goals, creating environments for success, and using evidence-based management to guide decisions. This mindset shift enables self-managing teams to thrive, delivering real value rather than just busywork.

Todd Miller and Ryan Ripley explore the role of conflict in Scrum teams, emphasizing that healthy conflict under pressure can drive focus and innovation. They discuss the importance of recognizing when disagreements shift from problem-solving to personal fights and stress the need for team members to maintain a commitment to constructive conflict.

Todd and Ryan discuss the power of self-managing teams, emphasizing that teams thrive when they have autonomy and direct access to customers, leading to higher productivity and better solutions. They caution that self-management is a skill that requires nurturing through coaching and support, rather than simply expecting teams to excel without guidance.

In Episode 12 of "Scrum is Hard and Disruptive," Todd Miller and Ryan Ripley discuss the importance of maximizing value by delivering only the highest value functionality, emphasizing the need to say "no" to unnecessary features.

In their latest episode, Todd and Ryan explain why Scrum is often harder than waterfall development, emphasizing that iterative processes require constant adjustments to engineering practices and architectural decisions. They highlight that Scrum forces teams to move away from over-planning and focus more on building and testing, which demands a disciplined and adaptive approach.

The video emphasizes that Scrum is a simple, adaptable framework that doesn’t need enhancement, unlike complex methodologies. Instead of altering Scrum, teams should focus on adding context-specific practices and addressing organizational impediments that hinder progress. The key message is to improve the environment in which Scrum operates, not the framework itself.

In the latest episode of "Scrum is Hard and Disruptive," Todd Miller and Ryan Ripley discuss how Scrum is not just a process to be implemented but a powerful tool to drive change within organizations. They emphasize that many companies misuse Scrum by treating it as another procedural rollout, failing to embrace its disruptive nature meant to challenge old business habits.

Todd and Ryan discuss the ongoing struggle of Scrum teams against ingrained Waterfall habits and predictive thinking that undermine Agile principles. Despite shifts in workforce generations and management styles, many teams still sacrifice quality to meet deadlines and rigid plans.

Scrum adoption requires top-down leadership but thrives with a “middle-out” approach that engages middle management to drive organizational change. Sustained effort and healthy conflict resolution are crucial, as the journey is ongoing and filled with challenges. To succeed, organizations must embed Scrum principles deeply enough that change continues effectively beyond the influence of any single individual.

This blog post explores how Scrum's intentional pressure on both engineering and product management teams drives continuous improvement and excellence. It emphasizes the importance of the "Definition of Done" and the need to close the "Effectiveness Gap" between current and target practices. Ultimately, the stress Scrum creates is a positive force that helps teams achieve better outcomes with each sprint.

Partial implementations of Scrum often obscure critical dysfunctions in product development, preventing teams from fully benefiting from the framework's potential. Scrum Masters are vital in identifying and addressing these issues, requiring experience and leadership to drive real change.

Scrum is more than a project management tool; it’s a competitive advantage that exposes organizational weaknesses and drives continuous improvement. Todd and Ryan emphasize that while Scrum highlights inefficiencies, true success requires adapting and addressing these issues rather than ignoring them.

In a recent episode of "Scrum is Hard and Disruptive," Todd Miller and Ryan Ripley discuss the provocative idea from Ken Schwaber's 2006 white paper that if the Waterfall methodology effectively meets a team's needs, it should be continued. The ultimate goal is to prioritize effectiveness and customer satisfaction, advocating for flexibility in delivery practices.

In their discussion titled "Scrum is Hard and Disruptive #2 - Complexity and Risk," Todd and Ryan explore how Scrum optimizes product management by emphasizing high-value delivery. They emphasize that while Scrum is designed for high-risk, complex projects, its success hinges on consistent product releases and iterative feedback loops to manage risks effectively.

In this video, Todd and Ryan explore Ken Schwaber's 2006 white paper, which discusses why Scrum is hard and disruptive. They use cross-functional, self-managing teams to emphasize Scrum's foundation in iterative and incremental development. Lean thinking and empirical process control are core principles, ensuring continuous improvement through frequent inspection and adaptation. The hosts draw parallels to real-life scenarios, like youth football coaching, to illustrate the effectiveness of self-managing teams.

Learn about cycle time and right-sizing Product Backlog items from Professional Scrum Trainers Todd Miller and Ryan Ripley.

Professional Scrum Trainers Ryan Ripley and Todd Miller explore how dependencies can impact the ordering of Product Backlog Items on today's episode of Your Daily Scrum.

The OBJECTIVE Framework highlights nine key components to successful goal setting: Outcome-focused, Balanced, Journey-oriented, Engaging, Challenging, Innovative, Timeboxed, Valuable, and Evaluated.

Learn about Laurens Bonnema's transformative journey in the Scrum world, from an unplanned start to becoming a successful Scrum Master and PST. His initial struggles and the lessons learned shaped his understanding and appreciation of the power of Scrum.

In a significant shift from their previous stance, Ryan Ripley and Todd Miller, hosts of "Your Daily Scrum," now advocate for integrating the role of Scrum Master with delivery managers and directors, countering their earlier advice to avoid this practice.

Todd, Ryan, and Prateek discuss throughput and why it is the most suitable flow metric for Sprint planning.

Professional Scrum Trainers Ryan Ripley and Todd Miller discuss the change from "estimate" to "sizing" in the 2020 update to the Scrum Guide.

Professional Scrum Trainers Ryan Ripley and Yuval Yeret discuss the role of the Scrum Master in the Scaled Agile Framework (SAFe) and how it differs from the role of a Professional Scrum Master.

Agile for Humans has launched a new YouTube series called SUCCESSFUL FACILITATION. Episode 4 explores a facilitation technique: Training From the Back of the Room.

Agile for Humans has launched a new YouTube series called SUCCESSFUL FACILITATION. Episode 3 explores a facilitation technique: Liberating Structure 1-2-4-ALL

Agile for Humans has launched a new YouTube series called SUCCESSFUL FACILITATION. Episode 2 answers the question: "What are Liberating Structures?"

Agile for Humans has launched a new YouTube series called SUCCESSFUL FACILITATION. Episode 1 answers the question: "What is facilitation?"

Everyone on the Scrum Team should level up their facilitation skills. In this video, Todd and Ryan explore why this skill is essential to a Scrum Team and how to improve in this critical area of complex work.

Why is the Scrum Master Role So Uncomfortable? Ryan and Todd discuss the hectic life of a Professional Scrum Master and their challenges when confronting complexity in an organization.

Every Scrum Team, at some point, will struggle with how to facilitate the Daily Scrum. By using a Kanban Board and Flow Metrics, Scrum Teams can better collaborate on their work, visualize progress towards the Sprint Goal, and form the best plan possible for the day.

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley address a general question in Scrum circles: What Does a Scrum Product Owner Do All Day?

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley teach you the Scrum Framework in 7 minutes!

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley debunk a general myth in Scrum circles: Creating a High Performing Scrum Team is NOT the Goal!

In a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley address a general question in Scrum circles: How Do You Increase the Velocity of a Scrum Team?

On a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley address a frequent question in Scrum circles: Why Do Organizations Fail at Scrum? 

Ryan Ripley and Neil Killick discuss the 3 levels of story slicing that all Product Owners can use to create great Product Backlog Items.

On a recent episode of Your Daily Scrum, Professional Scrum Trainers Todd Miller and Ryan Ripley address a prevalent question in Scrum circles: What is the Best Scrum Master Certification Path?

On a recent episode of Your Daily Scrum: Professional Scrum Trainers Todd Miller and Ryan Ripley address a common criticism of Scrum: Scrum isn't really agile, it's a command and control framework!

On today’s episode of YOUR DAILY SCRUM:  Is the Scrum Master Role an Entry Level Job?

On today’s episode of YOUR DAILY SCRUM: Planned vs Actual is a TERRIBLE Metric for Scrum Teams!

On today’s episode of YOUR DAILY SCRUM: What is the Real Cost of Context Switching for a Scrum Team? Today's question explores the real cost of context switching for a Scrum Team.

On today’s episode of YOUR DAILY SCRUM: When does UAT happen in Scrum? Today's question is all about User Acceptance Testing (UAT). UAT is an anti-pattern in Scrum.

On today’s episode of YOUR DAILY SCRUM: How Does a Scrum Team Handle Carryover Work? Today's question is all about carryover work. You know, the work that didn't quite get to DONE by the end of the Sprint.

On today’s episode of YOUR DAILY SCRUM:  Our Scrum Team is late! Should we add more people? Today's question asks whether or not a team running behind should add more people to try to get things completed faster.

On today’s episode of YOUR DAILY SCRUM: Can the Scrum Team skip their Sprint Retrospective?

On today’s episode of YOUR DAILY SCRUM: Can the Scrum Team skip their Sprint Retrospective?

On today’s episode of YOUR DAILY SCRUM:  How should a Scrum Team handle spikes? Today's question asks how a Scrum Team should handle SPIKES!?!?!

On today’s episode of YOUR DAILY SCRUM:  Does a Scrum Team need specialists or generalists? Today's question asks if we need specialists or generalists on a Scrum Team.

On today’s episode of YOUR DAILY SCRUM: What does a Scrum Master care about? Today's question asks what a Scrum Master truly cares about when working with a Scrum Team and the wider organization.

On today’s episode of YOUR DAILY SCRUM: How does a Scrum Team handle scope creep?