The Scrum Master role has quietly evolved, and the industry has not caught up. Kate Megaw and Ryan Smith unpack how the role calcified into a person who runs the events and works through a checklist, when the real job was always to be a change agent and an organizational catalyst. Look at the job market and you see the shift already happening. Scrum Master, Project Manager, Technical Project Manager, Delivery Manager, and Program Manager are being used interchangeably, because the title never fit cleanly on an org chart and the Scrum Guide 2020 move from roles to accountabilities went largely unnoticed.Kate and Ryan wrestle with a hard question. If the title confuses more than it clarifies, is it time to let it go? The word master implies telling rather than facilitating, and the name says nothing about what the person actually delivers. They also push back on the idea that agility is dying, making the case that it is becoming the DNA of healthy organizations instead. The takeaway is simple and a little uncomfortable. Stop defending the label and start demonstrating the impact a person in this role can have.

Velocity feels like proof.  Fifty story points done, a bigger number than last sprint, a box checked.  But velocity measures how busy a team is, not whether anything valuable reached the customer.  Kate Megaw and Ryan Smith take apart the metric everyone loves to report and rebuild the case for measuring what matters.  Velocity, they argue, was never a metric at all. It is an internal planning tool, Mike Cohn's “yesterday's weather”, useful for forecasting and useless for judging.  From there the conversation turns to the measures that actually signal agility: outcome over output, flow metrics like lead time, work in progress limits, emergent work per sprint, flow efficiency, and the strategic questions executives really care about, such as whether the business moved forward.  Along the way Ryan shares the MVP that 300 people found on their own, and Kate lands the question that cuts through it all: if your velocity doubled tomorrow, would your customers even notice? Velocity is vanity.  Outcomes are reality.  Agility lives in the flow.

There is “Big A” Agility, the frameworks like Scrum, Kanban, and SAFe, and there is “little a” agility, the plain human ability to change direction when the world shifts under your feet. Kate Megaw and Ryan Smith make the case that the second one matters most, and that it belongs in every company's core values, not just its delivery teams. Recorded ahead of Agile 2026 in Washington DC, whose theme is “Shaping the Future with Agility”, the conversation moves from VUCA to Bill George's VUCA 2.0, which answers volatility with vision, uncertainty with understanding, complexity with courage, and ambiguity with adaptability, to the most expensive words in business: “we have always done it this way”. Kate and Ryan dig into experimentation and the experiment log, why psychological safety is the ground everything grows from, the shift from a fixed mindset to a growth mindset, and why the five year plan and the pretty Gantt chart no longer survive contact with reality. The takeaway is simple. Shaping the future with agility is not about predicting what comes next. It is about building leaders, teams, and organizations that can thrive no matter what does.

Communication used to be filed away as a soft skill.  Kate Megaw and Ryan Smith make the case that it has become central to everything we do.  In a VUCA environment that is volatile, uncertain, complex, and ambiguous, communication is the anchor that keeps teams steady, and a recent Wiley survey found that 64 percent of people call it the single most important leadership skill.Kate and Ryan dig into why communicating well is harder than ever across hybrid, remote, and distributed teams.  They unpack the Mehrabian 7-38-55 rule and why a quick Slack can cost you most of your message, the rule of seven and how to repeat yourself without becoming noise, and the over-communication trap that trains people to tune you out.  You will walk away with practical habits for choosing channels, building two-way dialogue, and turning communication into part of your team's working agreement.  When things are stable, a team can survive weak communication.  Nothing is stable right now, so 

Kate and Ryan come at agility from opposite ends of the org chart. Kate arrived through training, operations, and project management on the leadership side. Ryan started as a front-end developer who built a Kanban board before he knew it had a name.  In this episode they trace Ryan's path from coder to Scrum Master, and dig into the questions every agile practitioner eventually asks.  Does a Scrum Master need to be technical?  What does the role really protect?  Why do so many transformations stall without a dedicated Scrum Master?Ryan makes the case that Scrum is agnostic to the work itself, that the Scrum Master creates the air the team breathes, and that the most important job is enforcing the pact between the team and the business so developers can do their best work without interruption.  He closes with practical advice for anyone growing into the role: go back to the Scrum Guide, get certified, and strip away the barnacles you have collected from role to role.