Troubleshooting Agile

They argue for stating the question first to cut through vague stories and get straight to the point. Examples show how a clear question helps people find their own answers and sharpens fuzzy problems. Practical habits like rubber-ducking and targeted context make conversations and meetings more efficient. Tips extend to product discovery and meeting design.

A conversation about using the board to drive focus and better standups. Practical contrasts between card-centered and person-centered status updates. How executive meetings can use boards to expose misalignment, side projects, and accountability gaps. Tips for building the habit and handling resistance to change.

A frank preview of a Helsinki unconference celebrating its 20th year and pivot to AI. They explain the open-space format and how topics get chosen. The conversation covers who shows up and why the crowd is unusually diverse and experienced. They debate the surge of AI in development and promise contrarian sessions and lively skepticism.

A lively conversation about what accountability really means and how fear teaches people to hide mistakes. They revisit a pivotal Kent Beck insight that reframes accountability as explaining your choices. The discussion covers leadership responsibility, how optimistic reporting masks problems, and practical communication practices like briefing and back-briefing.

A leaders' meeting goes off the rails and someone quietly thinks “what the fuck.” The hosts explore why people stay silent and how to break unproductive meeting patterns. They cover Parkinson's Law and bikeshedding, plus a 'walking the board' technique to keep discussions strategic. They encourage empowering quiet truth-tellers and embracing constructive disagreement to get to what matters.

They compare continuous sensors to manual dipstick checks using car maintenance as an analogy. They explore how continuous monitoring reduces surprises while periodic checks can let problems grow. They discuss alert fatigue, refining alerts to surface real issues, and designing on-call systems that get attention. They suggest automating important checks and tracking business usage metrics to catch declines early.

They explore why skillful practitioners struggle to teach beginners and how an expert blind spot forms. Playful metaphors like the Squirrelmobile are used to make abstract ideas tangible. Karate Kid and Shu‑Ha‑Ri parallels show the value of concrete beginner drills. Listeners are invited to share teaching wins and fails to build a practical toolkit.

A skiing mishap becomes a lesson in using the right tools for the job and checking basic assumptions. They explore how popular methods can be misapplied when context is ignored. Simple checklists and outside perspectives are highlighted as ways to catch blind spots and prevent embarrassing mistakes.

Daily feedback can transform how we develop software. Discover the value of rapid responses through an accidental upload mistake. Explore why quarterly reviews fall short and how frequent OKR checks can keep teams on track. Learn the glidepath indicator metaphor for making course corrections swiftly. The hosts emphasize shipping daily to get real customer reactions, while discussing the importance of measuring actual usage. Finally, witness the impact of user observation and how it can guide product changes.

Listener Tom raises concerns about the practicality of Vibe Coding and its perception in the tech community. Jeffrey shares insights from his experience with trivial tools that surprisingly enhance developer productivity. They delve into how small tools can kickstart large ecosystems, encouraging community growth and innovation. The discussion highlights the importance of simple libraries as indicators of a thriving environment. The hosts emphasize that initial outputs from new tools often lack value, recommending a cautious approach to adoption.