Story points = hours just makes sense though. Even if your team doesn't do it, then everyone will do it in their head anyway. Especially management. But everyone will have a different formula so you start arguing about how many story points something is. Just do it in the open.

[–] pixxelkick@lemmy.world 5 points 1 week ago

In the "right" use case, story points should just represent relative effort.

The hours dont matter, its more about ranking how challenging a task is, in order to help the manager rank the priority of tasks.

You should have typically 2~3 metrics:

Points, which represent relative effort of the task to the other tasks you are also ranking.
Value, how much value does doing this task provide, how important is it
Risk, how risky is it that this might break shit though if you make these changes (IE new features typically are low risk since they just add stuff, but if you have to modify old stuff now your risk goes up)

If you have a good integration testing system automated, Risk can be mostly removed since you can just rely on your testing framework to catch if something is gonna explode.

Then your manager can use a formula with these values to basically rank a priority order for every ticket you now scored, in order to assess what the next thing is that is best to focus on.

load more comments (5 replies)