---
title: "Why Story Points don’t make sense"
url: https://daily.dev/posts/why-story-points-don-t-make-sense-tixexknbr
source_url: https://levelup.gitconnected.com/why-story-points-dont-make-sense-117fabdac8ca
type: article
source: "Community Picks"
published: 2024-06-11T11:07:40.053Z
updated: 2024-10-05T18:58:46.434Z
tags: ["agile", "project-management", "scrum"]
reading_time: 1
upvotes: 37
comments: 6
language: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Why Story Points don’t make sense

**[Community Picks](https://daily.dev/sources/community)** · 1 min read · 37 upvotes · 6 comments

## Summary

The use of story points in agile estimation doesn't make sense because they can't be added up. Using t-shirt sizes instead of numbers can be a more accurate and consistent approach.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://levelup.gitconnected.com/why-story-points-dont-make-sense-117fabdac8ca>

## Community discussion

Top comments from developers on daily.dev.

**@jsnelders** · 13 upvotes

> I am yet to work in a business where story points and t-shirt sizes (if they were even used) were not then converted to time, because... the business always needs to know "how long" something will take.
> So we spend each planning session relatedly wasting a team's time arguing over the definition of each size, then arguing over the size of each item, only to turn around and turn it into time. 🤷‍♂️ Skip the BS and just work with time.

**@knute** · 8 upvotes

> We use fibonacci story point system and it seems to be far more accurate thru the duration of the sprint.
> 1 point: can complete multiple a day
> 2 points: one dev one day
> 3 : one dev a couple days
> 5: one dev one week
> 8: one dev one sprint

**@falbertengo** · 4 upvotes

> I use story points since forever, and quite successfuly, but not blindly. There are some caveats.
>
> The thing with story points is that they can describe more accurately situations taking expertise into account and can be used to median the technical/operational capacity of individuals and teams.
>
> Later, that measure can be used to estimate entire projects with great accuracy, specially if you have standardized tables of similar complexity features to reference to.
>
> But, I can't emphasize enough "technical capacity" because it's absolutely true that story points cannot be converted directly to...

## Similar posts on daily.dev

- [Don’t just attend KubeCon \+ CloudNativeCon, Merge Forward your experience\!](https://daily.dev/posts/don-t-just-attend-kubecon-cloudnativecon-merge-forward-your-experience--l0rpp73x8) · CNCF · 0 upvotes · 0 comments
- [Announcing H2 2026 KCDs](https://daily.dev/posts/announcing-h2-2026-kcds-m96goajm1) · CNCF · 1 upvotes · 0 comments
- [Two months of Open Community Groups](https://daily.dev/posts/two-months-of-open-community-groups-asf52zhbs) · CNCF · 0 upvotes · 0 comments
- [CNCF Unveils Schedule for KubeCon \+ CloudNativeCon Europe 2026](https://daily.dev/posts/cncf-unveils-schedule-for-kubecon-cloudnativecon-europe-2026-ikhcoa5cb) · CNCF · 2 upvotes · 0 comments
- [CNCF Debuts KubeCon \+ CloudNativeCon Japan 2026 Schedule](https://daily.dev/posts/cncf-debuts-kubecon-cloudnativecon-japan-2026-schedule-xp5pyudub) · CNCF · 1 upvotes · 0 comments

---

Tags: [#agile](https://daily.dev/tags/agile), [#project-management](https://daily.dev/tags/project-management), [#scrum](https://daily.dev/tags/scrum)

[View this post on daily.dev](https://daily.dev/posts/why-story-points-don-t-make-sense-tixexknbr)