You Think You Have a Velocity Problem. You Have an Undefined 'Done' Problem
Your velocity chart looks broken. Is the team actually slower — or did “done” quietly stop meaning the same thing to everyone?
Empowering Growth Through Education, Coaching & Development | Agile Coaching services
Browsing Year

Your velocity chart looks broken. Is the team actually slower — or did “done” quietly stop meaning the same thing to everyone?

She mapped the problem, built the solution, engaged the team. Then nothing moved. Here’s what nobody told her about her organisation.

A green build tells you the code works. It doesn’t tell you it solves the right problem. Here’s the gap AI widens.

You tightened AI adoption. Delivery didn’t move. Maybe the lever you pulled was never connected to your organisation’s real constraint.

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

Two client conversations, one lesson: no AI model or management conviction replaces listening before deciding how fast to move.

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.