3 ms·
My personal favorite “velocity” scapegoat is when the team can’t meet estimates but you’re constantly pushed to keep estimates as low as possible.
by devmor 3y ago
My personal favorite “velocity” scapegoat is when the team can’t meet estimates but you’re constantly pushed to keep estimates as low as possible.
- tikhonj 3y agoYeah, 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.
- ParetoOptimal 3y agoThe only people talking while setting points should be ICs and maybe the scrum master occasionally.
- bsdpufferfish 3y agoSo what does a scrum master do again?
- ParetoOptimal 3y agoMost important role is not letting managers attend points setting meetings IMO :D
- devmor 3y agostops ICs from talking about their idea for 40 minutes during standup