There's a really excellent discussion of story points, time, and why it's hazardous (at best) to center a team's KPIs around velocity on Ep. 15 of the Tech Done Right Podcast.
In a nutshell: Velocity alone doesn't tell you anything about the health of the team. And if you have enough other information to understand why you have the velocity you do, then velocity is actually less useful than those other metrics.
However a team measures velocity, it's vitally important that we also have other, complementary metrics to establish the health of the code and the team. Sarah Mei has been tweeting some excellent stuff about this stuff. I love her note on the goals of testing as an example of the trade-offs of how to center our daily practice around the team's core values.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's a really excellent discussion of story points, time, and why it's hazardous (at best) to center a team's KPIs around velocity on Ep. 15 of the Tech Done Right Podcast.
In a nutshell: Velocity alone doesn't tell you anything about the health of the team. And if you have enough other information to understand why you have the velocity you do, then velocity is actually less useful than those other metrics.
However a team measures velocity, it's vitally important that we also have other, complementary metrics to establish the health of the code and the team. Sarah Mei has been tweeting some excellent stuff about this stuff. I love her note on the goals of testing as an example of the trade-offs of how to center our daily practice around the team's core values.