What does story point mean to you?

Nothing, could be useful over time, if people aren’t leaving and joining, but that’s not the world we live in. Story points are almost anti science in how inaccurate their measurement is

Sir enjoy the f*cking weekend. Dont talk about work

it’s not inherently either. it’s a tool, it will be as effective as you make it out to be.

I've used it in the past, not anymore but I personally used to like it. In our case one story point was a very specific change, like adding a new butting to a UI, this might include CSS and JavaScript to make it work. We'd usually estimate as 5 points something more "complete" for example adding that same button plus the API backend to support it, plus any database schema changes needed, and maybe even include a prod deployment to land the complete change.

One word: Annoyance, PM should automatically be able to track time taken by devs to implement features, also Jeera bords should auto populate storypoints based on time taken in each 'status', they can even show some cool timeline per ticket, like 2 days 'in -dev' 1 day in review 0.5 day in qa and so on...

It can be better than the alternative - estimating in hours/days, if done right. That's a big if.

I like it, but the team needs to agree what they mean. I prefer a relative meaning with an anchor story used to set a starting point and you can always reference back to it even if the team changes. But most teams these days use story points as days which is frustrating but works well enough because it usually forces rounding up which is better than trying to be exact. The outcome is being able to gauge capacity and what you can do in a sprint realistically, if people are honest and not constantly rushing to finish everything.

My team does not care about points and we carry over tickets but it is good to know how long a task should take

Story points? Hard to make useful. Just give it a fibo rating of hours estimate. Shame so many techbros are dead scared of actually measuring work time.