Yeah, it's crazy how common that view seems to be in the industry for something that simply does not make sense. What people call "velocity" is an inherently r

Yeah, it's crazy how common that view seems to be in the industry for something that simply does not make sense. What people call "velocity" is an inherently relative measure, but they insist on treating it as an absolute. You can have a really slow team have a "great" velocity if their estimates account for moving slowly, and a fast team have awful "velocity" if their estimates are too short. Ultimately, it's a measure of something like predictability or consistency. Treating it as if it actually measures development speed is a category error. And hey, maybe consistency is what you want to prioritize over everything else! But, well, probably not.