At work we use story points (Fibonacci series) to estimate tasks. At first, when we were deciding between time and story points, I wasn't totally on board with

At work we use story points (Fibonacci series) to estimate tasks. At first, when we were deciding between time and story points, I wasn't totally on board with the idea of story points because the size of a point seemed completely ambiguous--you could even define 1 point to be an hour or day making them equivalent. Some argued a benefit was that our estimates couldn't be used against us if a task took longer than estimated. However, since a team velocity is tracked it seemed that the story points could still be converted to a time estimate. In the end though I have come to appreciate using story points, specifically Fibonacci points, for three main reasons: 1) Time estimates never seemed to be accurate; 2) In my experience it's easier to gauge relative complexity; 3) Using Fibonacci numbers inherently models the "fact" that larger tasks are harder to estimate. We use JIRA for tracking. I must say though in the end estimating things still always seems like a waste of time to some extent. I think it's more important to just have a prioritized backlog. I'm also always reminded of the following excerpt from the book Peopleware: https://news.ycombinator.com/item?id=14371140 https://news.ycombinator.com/item?id=14371140.