Из ленты dev.to devops — кратко, чтобы не потерять.
A VP I worked with once put two teams’ velocities on the same slide. Team A: 52. Team B: 28. He didn’t say anything mean. He just let the numbers sit there, side by side, and looked at Team B’s lead. Within two sprints, Team B was doing 50. Nothing shipped faster. They’d just learned that an 8 could be a 13 if you said it with confidence. Here’s the thing nobody tells you about velocity: it’s not a productivity metric, a commitment, or a number you can compare across teams. It’s a forecast with the error bars sawed off. And almost everyone reports it as if the error bars were never there. I’ve spent the last few years building agile estimation tools and watching teams do this to themselves. The pattern is always the same. The number is fine. What people do with the number is where it goes
Полный текст и контекст у первоисточника: https://dev.to/mattlewandowski93/your-velocity-number-is-a-probability-wearing-a-disguise-1ajj