Stripe gave Claude Fable 5 a real production task — migrating a 50-million-line Ruby codebase. It took one day. A human team would have needed two months. That single result reframes how Scrum teams should think about Sprint Planning, backlog ownership, and the Definition of Done. The article argues this isn't a threat to Scrum — it's its next evolution. Scrum Masters aren't being replaced; they're shifting from task managers to agent directors. The practitioners who develop that skill now will shape what Agile looks like for the next decade. AgileAIDev.com offers the training to make that transition.

Anthropic launched Claude Fable 5 on June 9, 2026 — the first publicly available Mythos-class AI model, previously restricted to government-approved partners. Unlike earlier AI tools, Fable 5 operates autonomously for days, planning and delegating tasks without constant human input. A real-world example: Stripe used it to complete a two-month codebase migration in a single day. For Scrum and Agile teams, the implication is significant — this isn't a smarter chatbot, it's an agent capable of running Sprint backlog items end-to-end, fundamentally changing what "done" means. The article frames learning AI-Enhanced Scrum as an immediate professional priority, pointing readers to AgileAIDev.com for training.

Learn how to use AI tools to run sharper Scrum ceremonies, coach smarter, and remove impediments faster. This live half-day session is built exclusively for working Scrum Masters and Agile Coaches. No prior AI experience required. Certificate included. $299.

Learn how to use AI tools to run sharper Scrum ceremonies, coach smarter, and remove impediments faster. This live half-day session is built exclusively for working Scrum Masters and Agile Coaches. No prior AI experience required. Certificate included. $299.

AI Agents Don't Replace Your Scrum Team — They Multiply It

Are you worried AI is coming for your Scrum team's jobs? You're not alone — but you're also wrong. And in this video, I'll show you exactly why.

After 30 years in software development and 15+ years as a Certified Scrum Trainer, I've seen every wave of technology that was supposed to make developers obsolete — CASE tools, offshore outsourcing, low-code platforms. None of them did it. But AI agents are genuinely different. Not because they replace your team, but because for the first time, you can add a tireless, always-on team member who ships work while your humans sleep.

In this video, I break down exactly where AI agents fit inside a real Scrum team — and more importantly, where they don't.

What you'll learn:

🔹 Why the fear is real — and why it's still wrong — AI agents are exceptional at complicated work: writing functions, generating tests, drafting documents. But complex problems — the kind Scrum was built for — still require human judgment, relationships, and context no AI currently has.

🔹 What the AI "team member" actually does in a Sprint — From Sprint Planning through Retrospective, I'll walk you through exactly how an agent plugs into each Scrum event: flagging acceptance criteria gaps, generating test stubs, surfacing sprint patterns your team missed, and preparing Sprint Review summaries your Scrum Master can edit and your Product Owner can present.

🔹 How the Scrum Master role evolves — You're still an impediment remover. But now you have a new category of impediment: non-human team member blockers. API rate limits. Failing Definition of Done checks. Prompt refinement problems. I call this agent stewardship — and it's not a smaller job. It's a bigger one.

🔹 The Product Owner's new superpower — A well-prompted agent turns a stakeholder conversation into a fully structured user story with acceptance criteria in under five minutes. It generates backlog risk analyses, flags under-specified stories, and writes the same feature from multiple user perspectives so your refinement sessions are richer than ever.

🔹 The one rule that keeps you in control — Every team that has struggled with AI has broken this rule. I'll tell you exactly what it is, and why following it changes your team's entire relationship with AI agents.

AI Agents Don't Replace Your Scrum Team — They Multiply It

Are you worried AI is coming for your Scrum team's jobs? You're not alone — but you're also wrong. And in this video, I'll show you exactly why.

After 30 years in software development and 15+ years as a Certified Scrum Trainer, I've seen every wave of technology that was supposed to make developers obsolete — CASE tools, offshore outsourcing, low-code platforms. None of them did it. But AI agents are genuinely different. Not because they replace your team, but because for the first time, you can add a tireless, always-on team member who ships work while your humans sleep.

In this video, I break down exactly where AI agents fit inside a real Scrum team — and more importantly, where they don't.

What you'll learn:

🔹 Why the fear is real — and why it's still wrong — AI agents are exceptional at complicated work: writing functions, generating tests, drafting documents. But complex problems — the kind Scrum was built for — still require human judgment, relationships, and context no AI currently has.

🔹 What the AI "team member" actually does in a Sprint — From Sprint Planning through Retrospective, I'll walk you through exactly how an agent plugs into each Scrum event: flagging acceptance criteria gaps, generating test stubs, surfacing sprint patterns your team missed, and preparing Sprint Review summaries your Scrum Master can edit and your Product Owner can present.

🔹 How the Scrum Master role evolves — You're still an impediment remover. But now you have a new category of impediment: non-human team member blockers. API rate limits. Failing Definition of Done checks. Prompt refinement problems. I call this agent stewardship — and it's not a smaller job. It's a bigger one.

🔹 The Product Owner's new superpower — A well-prompted agent turns a stakeholder conversation into a fully structured user story with acceptance criteria in under five minutes. It generates backlog risk analyses, flags under-specified stories, and writes the same feature from multiple user perspectives so your refinement sessions are richer than ever.

🔹 The one rule that keeps you in control — Every team that has struggled with AI has broken this rule. I'll tell you exactly what it is, and why following it changes your team's entire relationship with AI agents.

Rod Claar traces a through-line from his earliest work in a 1972 lumber yard to his current role as an AI trainer — revealing that the core skill connecting both worlds is pattern recognition. The post reframes AI for skeptics and late adopters: AI isn't magic, it's pattern matching at scale. Professionals with decades of real-world problem-solving experience already possess the foundational thinking that makes AI useful. The message is empowering — your past experience is an asset, not a liability, in the age of AI.

Five facts from the past week — a stronger Claude, metered Copilot billing, a cheap new Grok coding model, a more autonomous Cursor, and a permanent DeepSeek price cut — and what each means for your Scrum team.

Rod Claar draws a direct parallel between writing clean code and writing effective AI prompts. The core idea: vague instructions produce broken results, whether you're coding or prompting. Developers already have the structured thinking required to write great prompts — they just need to apply it to AI. The post offers four practical rules for better prompts and closes with a concrete example showing the difference between a weak prompt and a precise, program-like one.

Over a 50-year career spanning lumber yards, retail software, Scrum and AI-assisted development, one principle has remained constant: the best professionals think clearly about the problem before reaching for a tool. Whether it was a pencil and clipboard in 1972 or AI in 2026, the tool itself was never the differentiator — the quality of thinking behind it was. The same holds true today: great developers define the problem before opening an IDE, write tests before writing code, and ask AI a good question before accepting its answer. Tools will keep changing. Clear thinking never goes out of style.