Troubleshooting Agile: Podcast Review

What if the biggest obstacle to becoming more agile is not your process, but the conversations, assumptions, and habits surrounding it? In Troubleshooting Agile, hosts Jeffrey Fredrick and Douglas Squirrel bring years of software, leadership, and organizational experience to the everyday problems that keep agile teams from working as effectively as they could.

What is the Podcast About?

Troubleshooting Agile is a practical problem-solving podcast for people working in agile teams, particularly those navigating the messy realities of software development, product delivery, leadership, and organizational change. Rather than treating agile as a fixed collection of ceremonies and rules, Jeffrey Fredrick and Douglas Squirrel examine what actually happens when teams struggle to ship, communicate poorly, avoid difficult questions, misunderstand customers, or adopt practices without understanding why they matter. Episodes typically begin with a recognizable problem and develop into a focused conversation about what might really be causing it.

The scope extends well beyond Scrum boards and sprint planning. Fredrick and Squirrel explore continuous delivery, testing, accountability, team engagement, management, difficult conversations, product decisions, feedback loops, artificial intelligence, organizational learning, and the relationship between technical practices and human behavior. Their goal is consistently practical: identify what is going wrong, challenge the assumptions behind it, and offer approaches that listeners can experiment with immediately. This makes the show less like a course in agile methodology and more like an ongoing troubleshooting clinic for the realities of modern teamwork.

Podcast Details

Category: Business
Frequency: Weekly
Starting Year: 2017
Language: English

Podcast Creator

Core Theme

At the heart of Troubleshooting Agile is a deceptively simple philosophy: when a team has a recurring problem, merely adding another process is rarely enough. The hosts repeatedly look beneath visible symptoms to examine the assumptions, incentives, communication patterns, feedback loops, and leadership behaviors that sustain them. Whether they are discussing daily demonstrations, accountability, testing in production, product interfaces, AI adoption, or a team’s reluctance to challenge a decision, the deeper question remains similar: what prevents this group from learning from reality quickly enough to change what it does?

That perspective makes conversation itself one of the podcast’s most important themes. Fredrick and Squirrel emphasize curiosity over premature certainty, joint problem-solving over persuasion, and experimentation over abstract debate. Agile, in this view, is less about perfectly following a methodology and more about creating conditions in which information travels quickly, assumptions can be challenged safely, failures become useful evidence, and people can adapt their behavior as circumstances change. The result is a philosophy of agility that connects technical excellence with emotional intelligence, leadership, accountability, and continuous learning.

Podcast Takeaways

Some key lessons from the Podcast:

• Diagnose before prescribing: A team’s visible problem may only be a symptom, so effective improvement begins by understanding what is actually producing the difficulty rather than immediately reaching for another framework or ceremony.
• Make feedback faster: Short feedback loops, frequent demonstrations, continuous testing, and direct exposure to real outcomes help teams discover mistakes while they are still inexpensive and manageable.
• Ask better questions: Teams become more effective when they question the assumptions behind a request instead of automatically accepting the question, requirement, or proposed solution as given.
• Treat conversation as an engineering tool: Clear, curious, and candid communication can expose misunderstandings and coordination problems that no project-management system can solve on its own.
• Make accountability mutual: Healthy organizations do not reserve accountability for employees. Leaders must also examine their decisions, assumptions, communication, and contribution to the systems they oversee.
• Turn failure into information: Documenting and examining what went wrong creates opportunities for learning, especially when the goal is understanding rather than assigning blame.
• Use technology with judgment: Whether adopting AI, automation, testing practices, or new product interfaces, teams should evaluate technology according to the problem it solves and the feedback it produces rather than following enthusiasm or fashion.

Podcast Strengths

One of the greatest strengths of Troubleshooting Agile is its ability to make complex organizational problems feel concrete without pretending they have simple formulas. The episodes are generally compact and focused, yet Fredrick and Squirrel draw on substantial experience in software development, consulting, leadership, and team dynamics to give their discussions depth. Their conversational format also works especially well because disagreement, questioning, stories, analogies, and real workplace situations become part of the learning process. Listeners have praised the show for being practical, thought-provoking, candid, and free of unnecessary filler, and that practicality is central to its appeal: the hosts are interested in ideas primarily because of what happens when real teams try to use them.

Who This Podcast Is For

Troubleshooting Agile is particularly valuable for software engineers, engineering managers, product leaders, Scrum Masters, agile coaches, consultants, founders, and executives who want to understand why teams behave the way they do rather than simply learn another set of agile techniques. It should also appeal to anyone responsible for improving collaboration, delivery, or organizational learning. Experienced practitioners may appreciate the hosts’ willingness to challenge familiar agile assumptions, while newcomers can gain a more realistic picture of agility as an evolving way of solving problems rather than a checklist that can be implemented once and considered finished.

Why Should You Listen To This Podcast?

You should listen to Troubleshooting Agile if you want ideas that can survive contact with an actual workplace. Instead of presenting an idealized version of agile, Fredrick and Squirrel spend their time in the uncomfortable territory where communication breaks down, managers and teams misunderstand one another, delivery slows, fashionable tools create unexpected problems, and seemingly sensible practices produce disappointing results. The relatively short episodes make it easy to explore one problem at a time, while the hosts’ emphasis on experiments, questions, feedback, and conversation gives you something more useful than theory alone. You come away not merely with another technique to copy, but with a sharper way of examining what is happening inside your own team.

Questions This Podcast Helps Us Explore

1. What if many of our process problems are actually communication problems wearing different names?
2. How can a team distinguish between genuinely useful agile practices and rituals it follows simply because they have become familiar?
3. What changes when leaders become as willing to question their own assumptions as they are to evaluate their teams?
4. How can failure become a source of organizational intelligence rather than something people learn to hide?
5. What would work look like if agility were measured by our ability to learn and adapt rather than our ability to follow a prescribed process?

Concluding Thoughts

Troubleshooting Agile succeeds because it treats agility as a living practice rather than a finished methodology. Across hundreds of episodes, Jeffrey Fredrick and Douglas Squirrel keep returning to the situations where theory becomes difficult: imperfect information, uncomfortable conversations, changing technology, organizational politics, leadership mistakes, customer uncertainty, and the stubborn habits that prevent teams from learning. Their response is rarely to prescribe more complexity. Instead, they encourage listeners to observe more carefully, question more intelligently, communicate more openly, and shorten the distance between action and feedback.

That approach gives the podcast relevance far beyond agile software development. At its deepest level, the show is about how groups of people learn to confront reality together without becoming trapped by certainty, hierarchy, or habit. For anyone responsible for building products, leading teams, or improving how an organization works, Troubleshooting Agile offers a steady stream of small but meaningful challenges to conventional thinking. Listen with a current workplace problem in mind, and there is a good chance the show will help you see a different question hiding underneath it.

→   You can listen to Troubleshooting Agile on Apple Podcasts and other leading platforms, or explore more at their website.

Chief Editor

Tal Gur is an impact-driven creator at heart. After trading his daily grind for a life of his own design, he spent a decade pursuing 100 life goals around the globe. Tal's journey and recent book, The Art of Fully Living, inspired him to found Elevate Society.