I'm not saying it's useful, just that I found out it was a metric for management. I was originally expecting it to be an internal metric. The company I was at a

I'm not saying it's useful, just that I found out it was a metric for management. I was originally expecting it to be an internal metric. The company I was at actually used it in performance reviews somewhat comparable to stack ranking. There was an expectation that devs complete about 8 points a sprint. I don't know if the eight point target is common, but SAFe does talk about comparing story points across teams. > At scale, it becomes difficult to predict the story point size for larger epics and features when team velocities can vary wildly. To overcome this, SAFe teams initially calibrate a starting story point baseline where one story point is defined roughly the same across all teams. ... > Give every developer-tester on the team eight points for a two-week iteration https://www.scaledagileframework.com/story/ https://www.scaledagileframework.com/story/