Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There should be a special circle in hell for companies abusing velocity as a metric. Story points are made up points and looking at their velocity or acceleration will result in noise. Managing that noise may look useful, however, it is waste of time. It is as useful as going to the seaside and writing reports on underperforming waves.

What is useful, is to understand why certain task take longer than anticipated and learn lessons from that. Were there hidden requirements or was the task too ambitious and should it have been broken down in smaller tasks.



My favourite is the "velocity of money" in macroeconomics. Shocking misuse of the word!


That’s an entirely separate concept from dev velocity. FWIW I like the name in economics, and can’t immediately think of a much better one.


Frequency is a better term. The dimensions are 1/Time.


If you define distance (wrt money) as the number of people it’s passed through, then it has the appropriate units.


I prefer to think of it as the reciprocal of "residence time", that is how long the money spends at rest in a given account (on average).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: