Agile – The Software Coach

AI can write a user story. It can’t have the conversation that makes it mean something. A case study in distance.

AI makes your team faster. It won’t tell you what’s worth building. Here’s why the backlog question still comes first

Your team’s “10x” AI-accelerated capacity isn’t stable — it fluctuates unpredictably. Is your planning accounting for that?

AI coding assistants promise faster delivery. But what if coding was never the bottleneck? A queueing theory perspective.

Are AI coding assistants reducing variation in your team — or just making it invisible? The evidence cycle is younger than you think.

Knowing there’s a better way isn’t enough. What stops teams from changing — even when the cost of staying stuck is obvious?

Why do teams cling to broken processes? A UCL study explains more about software delivery than you might expect.

A static Definition of Done produces static results. An evolving one creates productive crises that force teams to improve sustainably.

Two years of agile transformation delivers the structure. Lasting change requires building the capability to keep improving. Here’s the difference.

When sprint planning focuses on scope instead of value, mid-sprint becomes scope arguments. Here’s what planning should actually achieve.