AI Broke Story Points. Now What?
For years, story points (love them or hate them) have been a cornerstone of agile planning. Teams use them to estimate effort, forecast delivery, and measure velocity over time. While the practice has never been perfect, it has generally worked because one assumption remained true: effort was relatively predictable.
Artificial intelligence is starting to change that.
Developers can now generate code, create tests, write documentation, and analyze requirements faster than ever before. Tasks that once required hours or days of work may now take minutes. The result is not just faster delivery; it is a fundamental shift in how effort is applied to software development.
That creates an uncomfortable question for agile teams. If story points are meant to represent effort, what happens when effort suddenly becomes harder to define?
A five-point story completed today with AI assistance may require significantly less work than the same five-point story did a year ago. Teams may see velocity increase. But does that mean they are more productive, or does it mean the metric itself is becoming less meaningful?
As organizations rush to embrace AI, many are focused on what it can do for delivery speed. Far fewer are asking what it means for the measurements they rely on. Story points may not be dead, but AI is forcing teams to rethink what they actually represent.
The
Please log in or sign up below to read the rest of the article.
|
There are two ways of spreading light: to be the candle or the mirror that reflects it. - Edith Wharton |




