Rethink Your Understanding

When companies remove Agile Leaders, roles like Scrum Masters or Agile Delivery Managers, they often assume the system will self-regulate. But what really happens when no one is accountable for team health, continuous improvement, or flow?In this episode, the AI hosts unpack Phil's article about the quiet erosion of agility inside modern organizations, where well-intentioned efficiency moves end up dismantling the very disciplines that make agile work. Drawing from real-world transformations, he argues that while frameworks fade, the mindset of agile leadership must endure.Link to the article: What Happens When We Eliminate the Agile Leader?, originally published October 09, 2025.Connect with me on LinkedIn

AI’s full potential in software delivery isn’t in writing code faster, it’s in transforming the entire value stream. In this episode, the AI hosts explore why most delays happen in ideation and release, not coding, and how AI applied narrowly to delivery can actually amplify dysfunction. Drawing on insights from Mik Kersten, Laura Tacho, John Cutler, Atlassian’s 2025 AI Collaboration Report, and the DORA 2025 findings, we discuss how leaders can use Value Stream Management and flow metrics to measure AI’s true impact, reduce systemic waste, and accelerate idea-to-value across the enterprise.Link to the article: Beyond Delivery: Realizing AI’s Potential Across the Value Stream, originally published September 30, 2025.Connect with me on LinkedIn

This episode takes you inside the evolving role of a VP of Engineering — far beyond a standard job description.The AI hosts discuss why the role is highly contextual, shaped by company size, leadership culture, and organizational maturity. I share the core accountabilities I’ve been held to: ensuring software quality and resilience, fostering people engagement, retaining and developing talent, and building the skills teams need to stay competitive.The conversation also explores the VP’s strategic importance in business alignment, global talent management, and transformation initiatives, while contrasting the role with that of a CTO. Finally, we touch on the personal evolution required to succeed — developing V-shaped skills, mentoring leaders, and balancing the rewards of culture-building with the challenges of tough decisions.Link to the article: So, What Does a VP of Engineering Do?, originally published August 21, 2025.Connect with me on LinkedIn

AI is transforming software engineering, but it addresses only one part of a much larger system. Speeding up code creation doesn’t solve deeper issues like unclear requirements, poor architecture, or slow feedback loops, and in some cases, it can amplify dysfunction when the system itself is flawed. Engineers remain fully responsible for what they ship, regardless of how the code is written. The real opportunity is to increase team capacity and deliver value faster, not to reduce cost or inflate output metrics.The bigger risk lies in how senior leaders respond to the hype. When expectations are driven by buzzwords instead of measurable outcomes, focus shifts to the wrong problems. AI is a powerful tool, but progress requires leadership that stays grounded, focuses on system-wide improvement, and prioritizes accountability over appearances.

In this episode, our AI hosts dive into an article advocating for a radical reevaluation of software delivery commitments, shifting away from rigid, project-based models and “precise” estimates toward a probabilistic, continuous-discovery mindset. Drawing on Vasco Duarte’s insights and the Three Ways outlined in The DevOps Handbook, they explore treating development as a series of adaptive bets, budgeting for change, using experiments as real-time status reports, and empowering end-to-end team ownership to achieve true agility and align work with value streams.Link to the article: Bets, Budgets, and Reframing Software Delivery as Continuous Discovery, originally published June 07, 2025.Connect with me on LinkedIn

This episode addresses a common pitfall in software delivery management: using system-level metrics, such as Flow Metrics, to evaluate individual performance. The AI hosts cover how this practice, while logical to some leaders, can damage trust, produce misleading data, and hinder real improvement. The conversation covers using metrics as a tool to help teams improve, focusing on context, collaboration, and actionable steps. The main takeaway is clear: metrics should promote overall improvement, not serve as personal performance scores.Link to the article: We Have Metrics. Now What?, originally published May 11, 2025.Connect with me on LinkedIn