# story points

Published articles for story points.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Why teams can create more impact by stopping work estimates

DevFeed: [Why teams can create more impact by stopping work estimates](<https://devfeed.tech/articles/how-to-drive-more-impact-without-ever-talking-about-nonsense-numbers-40048.md>)

Original publisher: [Read original article](<https://dpereira.substack.com/p/why-estimations-are-irrelevant>)

Author: David Pereira

Published: 2026-07-09T12:45:21Z

Content type: opinion

Language: en

Sources: [Untrapping Product Teams](<https://devfeed.tech/sources/untrapping-product-teams.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [sessions](<https://devfeed.tech/topics/sessions.md>)

Tags: [development](<https://devfeed.tech/tags/development.md>), [scrum](<https://devfeed.tech/tags/scrum.md>), [sessions](<https://devfeed.tech/tags/sessions.md>), [story-points](<https://devfeed.tech/tags/story-points.md>), [velocity](<https://devfeed.tech/tags/velocity.md>)

### AI overview

The article argues that estimates, story points, velocity, and capacity planning can create false expectations and constrain teams. It describes an experiment removing estimates from a refined backlog to encourage smoother collaboration and greater focus on value.

### Source excerpt

How teams maximize impact without wasting energy sizing work.

## Ways to Decrease Performance: Velocity Tracking

DevFeed: [Ways to Decrease Performance: Velocity Tracking](<https://devfeed.tech/articles/ways-to-decrease-performance-velocity-tracking-39954.md>)

Original publisher: [Read original article](<https://mende.io/blog/ways-to-decrease-performance-velocity-tracking/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2023-07-15T06:00:00Z

Content type: opinion

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [Agile](<https://devfeed.tech/topics/agile.md>), [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>)

Tags: [agile](<https://devfeed.tech/tags/agile.md>), [article](<https://devfeed.tech/tags/article.md>), [critical](<https://devfeed.tech/tags/critical.md>), [measuring](<https://devfeed.tech/tags/measuring.md>), [metrics-practices-ways-to-decrease-performance-developer-productivity-engineering-excellence](<https://devfeed.tech/tags/metrics-practices-ways-to-decrease-performance-developer-productivity-engineering-excellence.md>), [performance](<https://devfeed.tech/tags/performance.md>), [practices](<https://devfeed.tech/tags/practices.md>), [story-points](<https://devfeed.tech/tags/story-points.md>), [teams](<https://devfeed.tech/tags/teams.md>), [velocity](<https://devfeed.tech/tags/velocity.md>)

### AI overview

This opinion article examines velocity tracking and estimation in Agile software teams. It explains how teams use story points, velocity trends, and burndown charts, then begins discussing how these practices can harm performance, including the limitations of human estimation.

### Source excerpt

Ways to Decrease Performance: Velocity Tracking This is the first article of my series, "Ways to Decrease Performance", which intends to trigger critical reflection on common "Agile" practices, that is, practices that I see many "agile" teams doing.