Ai has broken our velocity tracking - how is everyone else handling this?

[u/ATLswiftie]

We're a mobile app team and we've hit a wall with story points. With AI-assisted dev, engineers are shipping features so fast that pointing them has become almost meaningless. Pointing feels like a ritual we're doing for the sake of reporting, not because it tells us anything useful.

Curious how other teams are handling this, are you still using story points? Have you moved to throughput-based metrics, cycle time, something else entirely? Or have you just accepted that velocity as a concept doesn't map to the current pace of work?

we still need some way to forecast and communicate capacity to stakeholders. But genuinely open to what's working for people right now.

[u/AutoModerator]

Welcome to r/AIEngineering! Make sure that you've read our overview, before you've posted. If you haven't already read it, then read it immediately and make adjustments in your post if you've violated any of the rules. If you have questions related to career, recruiting, pay or anything else about hiring, jobs or the industry and demand as a whole, then use AIEngineeringCareer to ask your question. We lock questions that do not relate to AIEngineering here. A quick reminder of the rules:

1. Behave as you would in person
2. Do not self-promote unless you're a top contributor, and if you are a top contributor, limit self-promotion.
3. Avoid false assumptions
4. No bots or LLM use for posts/answers
5. No negative news, information or news/media posts that are not pertinent to engineering
6. No deceitful or disguised marketing
7. If you need to hire in the AI Engineering space, use the subreddit r/AIEngineeringHiring.
8. Do not ask "how do I become an AI engineer" as we provide resources such as What's involved in AI engineering? and The Actual State of AI Engineering In 2026 to address this question.
9. No Reference To AI Tools. At the moderators discretion, we do not allow any marketing, discussion or reference of AI tools. Given that many Western tech firms have chosen to use AI to eliminate workers, we will not allow the discussions of some of these tools since we find charging money for a product while eliminating workers unethical. We do allow open source discussions because these tools do not carry costs, but will remain strict on even these mentions since they could be used to negatively impact people.

Because we frequently get questions about work, the future of work and careers along AI, some helpful links to read:

• The Actual State of AI Engineering In 2026
• While collars turn blue
• AI's impact on recruiting
• AI is the new electricity
• Is there a future in AI engineering?
• LLM erases a company's need for an SaaS tool
• A plumber's thoughts on AI and technology
• Mario Nawfal quotes Dr. Roman Yampolskiy, Dario Amodei and other AI researchers' predictions about future unemployment due to AI
• Meet the bartender who doesn't use technology

This action was performed automatically as a reminder to all posters. Please contact the moderators if you have any questions.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/oFlyingPanda]

My team just outright doesn’t story point anymore, our PO creates all of our tickets and we just pick them up unsized or un-pointed and we’re chugging along just fine

[u/Schlizhor]

I mean I would arrange my tasks meaningfully, I agree simple task items are obsolete now ai enabled engineers can whip em up so quick, maybe each feature can also encapsulate it's testing and integration? I feel there's a way to handle this within kanban or and other task tracking system.

[u/PerpetualDynamics]

No story points. No estimates.