The article argues that recent AI advances are moving software development from simple code completion to agent-driven delivery. AI tools are now better at planning, editing code, testing, debugging, reviewing, and creating pull requests across larger codebases.

The five main changes are:

1. AI coding agents are handling more complex engineering work, which means teams need clearer backlog items, acceptance criteria, constraints, and tests.
2. AI agents are entering enterprise infrastructure, so organizations must create rules for repo access, data use, security, compliance, and human review.
3. IDEs are becoming control rooms for remote agents, shifting developers toward task delegation, review, and decision-making rather than writing every line of code themselves.
4. AI coding cost is becoming part of planning, as usage-based billing makes agent activity a budget concern.
5. New research shows AI agents are powerful but risky, with generated code often needing correction and potentially introducing security issues.

The central message is that Scrum and Agile practices become more important, not less. Teams that succeed will use AI deliberately, with tight feedback loops, visible acceptance criteria, strong review practices, automated tests, and clear working agreements.

Rob Pike's 5 Rules — What They Mean for AI and Agents

Rob Pike wrote five rules for writing clean C code in 1989. They hold up surprisingly well today — especially now that AI tools and autonomous agents are showing up in our Sprints, our pipelines, and our backlogs.

Rule 1: Bottlenecks are never where you think. Before your team celebrates an AI cutting story-writing time in half, check your cycle time data. The real delay is usually in review, refinement, or deployment — not the thing you just automated.

Rule 2: Measure before you tune. Don't add AI everywhere at once. Run a few controlled Sprints, look at velocity and defect rates, then decide. Your Retrospective already gives you the structure to do this.

Rule 3: Fancy is slow when n is small. Large language models are expensive and complex. A simple query or regex handles a lot of small tasks faster and cheaper. AI earns its keep on genuinely large, messy problems — not ten-line standup summaries.

Rule 4: Fancy algorithms are buggier. AI-generated code looks polished and can still be wrong. TDD and ATDD are your safety net. Write the test first, let the AI write the code, and let the test decide if it worked.

Rule 5: Data dominates. Clean up your backlog before you trust AI to read it. Well-written user stories and consistent acceptance criteria produce better AI output. No model compensates for messy data.

The bottom line: Pike's rules and the Scrum framework are pointing at the same thing — measure, keep it simple, test rigorously, and treat your data as the foundation everything else rests on.

This course page promotes Rod Claar's Certified ScrumMaster (CSM) class, offered in both virtual and in-person formats. It's built for anyone on a product development team — from beginners to those who want to sharpen their Scrum skills.

Virtual training is highlighted for its flexibility, cost savings, and convenience — no travel required. New options include a half-now/half-later payment plan and a Gold Plan that bundles up to 8 hours of one-on-one coaching with the instructor in the 60 days after class.

What you'll learn covers the core of Scrum — why it works, the roles of the ScrumMaster and Product Owner, and how to handle real-world challenges when rolling out Scrum in an organization.

Organizations sending 3 or more people can take advantage of a customized Private Team Session.

Graduates earn 14 PDUs and gain access to the Scrum Alliance CSM exam — an online, open-book test. Passing it earns the official Scrum Alliance Certified ScrumMaster (CSM) credential.

The page closes with a bold promise: instructor Rod Claar, CST, will personally work with every student until they pass the exam — or until one of us dies!