Let's all head to the conference room, so we can discuss the definition of a story point for an hour. I'd also like to talk about why we are behind schedule and our velocity is dipping. Let's make it two hours.

[–] vithigar@lemmy.ca 1 points 1 day ago* (last edited 1 day ago) (3 children)

Management where I work finally unbent and admitted that story points were time.

...but also want to continue raising velocity in each sprint.

[–] normalexit@lemmy.world 1 points 1 day ago

Sounds like a good time to start padding estimates.

[–] NotMyOldRedditName@lemmy.world 1 points 1 day ago

I don't even see why them roughly representing time is a problem due to them raising in a fibonacci sequence.

If they were a day each, it's not like the jump from 5 to 8 means it's going to take 3 more days, but that it's gotten more complex and maybe it'll still be 5 or 6 days but I can't be sure because this one has a lot more unknowns that might not reveal themselves until I'm into it. That's why we're forced to go from 5 to 8 and not a 6 or 7.

The uncertainty is built right into it, so it can't be exact time, but at the same time trying to ignore that they're still time related is stupid.

[–] chilicheeselies@lemmy.world 1 points 1 day ago (1 children)

Dont worry, they are unserious about actual results; they just care about the appearance of results that they can report up. Just start padding extra... Fucking story points...jesus.... To each ticket. Now everyones charts look like their velocity increased. Dont worry, noone is actually measuring results.

[–] vithigar@lemmy.ca 2 points 1 day ago

That's exactly what we ended up doing. Every story has now become one Fibonacci step higher than it would have been before.