3 ms·
One thing that stuck out to me is how consistent the numbers became between each other under WFH. I am not familiar with the metric or scrum, but I wonder what
by dkn775 6y ago
One thing that stuck out to me is how consistent the numbers became between each other under WFH. I am not familiar with the metric or scrum, but I wonder what the cause is?
- klenwell 6y agoI noticed that, too. I think that's mostly coincidence. Velocity is based on story points. Here's a definition of story points as a unit of measure that I like: A Story Point is a relative unit of measure, decided upon and used by individual Scrum teams, to provide relative estimates of effort for completing requirements. https://www.scrum.org/resources/blog/why-do-we-use-story-points-estimating https://www.scrum.org/resources/blog/why-do-we-use-story-poi... It is generally recommend you not include time as a component of that unit. For our teams, we kinda do. (Basically, for us, story point = time + uncertainty + complexity.) So there is a common standard. But with scrum you're supposed to size stories relative to other (previous) stories and I feel it's ok for the standard measure of a story point to drift apart between teams as long as its internally consistent to the team. So maybe there's some kind of leveling force at work. But probably not.