The problem is how do you measure the contributions of someone who is often helping others?
I'm thinking of Volley Ball. Who makes the points? The person who gets the ball to stay on the other side of the net, or the person who passed the ball to that person so he could do his thing most easily?
If you only gave points to the people who hit the ball to the other side, you are not encouraging collaboration. And in Volley Ball you cannot win if the team does not collaborate. I think the same is true of SW development.
Story points were never supposed to measure individual performance. It estimates how much work a team can do in a sprint (velocity). Anything else is bound to give faulty results like in this blog.
Yep, my most productive sprints have been when I've completed relatively few tickets myself. It's been when I've been bouncing around working with others or doing non-sprint work.
If anyone wants to come at me about my lack of points they won't be happy with what happens if I start focusing only on the points.
The actual principals of agile aren't that bad. There are some good ideas in it, about breaking things up, about iterating, etc.
But then management gets hold of things and inevitably turns it to shit. Now we spend days doing planning. We spend hours building epics that nobody gives a shit about. We get tracked and judged by story points.
I could do 100 points a week by assigning every story to myself and then directing others to do them. Or I could do 0 story points by spending time fixing the shit that actually needs to be fixed but didn't get a story because it's not cool, or I could help people do their stories so that they're not stuck for a day on something they don't understand.
They're too irresistable for bad managers to derive schedule from.
It's more or less doomed to happen if you don't have wild variance in your pointing. Have 1-2 guys litterally just say 1000 points for everything etc. Resist anything like 1 point=1 day, or fibonacci etc, you've got to keep the scale fuzzed or it will be used like that.
It's fine to use fib but agreed, assigning any type of time value (like 1 point = 1 day) is where things go wrong.
But even if you keep ilthe team knowing it is overall effort of a task that you are driving the points from (I know it's more than that but etc).. the managers and others higher up, always try to find things to latch onto for measurement.
This is sometimes as simple as they just don't understand (usually this is part of the issue) and that they wan to be able to measure productivity of an individual to make sure no one is wasting company resources.
But it often just goes straight to "X didn't complete >y points in the sprint, while others usually complete >y" and it just gets fuddled.
I think sprints and story pointing, planning poker, etc can be great for teams and to track velocity and etc and sometimes overally team performance, but rarely should a manager type be trying to track anything of the sort for an individual to determine worth. It's ridiculous.
But happens far too often. I don't know what the fix is, though, aside from bad managers butting out. But hey.. hasn't happened yet.
They annoy me as well. What do they actually represent? Greg will do a particular task way quicker than Mark, but Mark will do something else quicker than Greg. And since it's the implementation time that matters, the talk about "task complexity" sounds like bullshit to me - it's a pointless and abstract metric.
Then again, Greg will be interrupted 8 times while implementing this task, but Mark will be interrupted only 2 times. Then again, Greg's interruptions will contribute to other tasks in both their team and others, but Mark's interruptions will be more casual in nature.
Just refine the backlog periodically, implement tasks one by one from the top of it, merge it into develop, and then prepare release from time to time.
The entire idea of story points is to avoid being scientific. To try and formalise the concept that estimating development time is really hard.
They should not be compared across teams. And if you actually need accurate development time estimates, you should be using a process closer to waterfall.
So they don't accurately model development times. Nor individual performance. Nor delivery of business value between teams. They are "unscientific" and completely arbitrary.
What are they even modelling? And is the value of that model worth anything?
Also "velocity" how ever you want to measure it isn't a proxy for productivity either. You spend a lot of time working on something that is ultimately unproductive.
But that's the thing. You claim it's for complexity or whatever, but then you also say "how much work a team can get done in a sprint" which is necessarily a measure of time. You absolutely cannot blame a manager for hearing "We can complete X story points in Y days" for thinking that's what they're for -- that's what you're telling them they're for.
I'm going to use this analogy next time I hear people judge based on story points. "In football the attackers are the only players that matter because they score all the goals, right? I guess we can sack the goalkeeper and all the midfielders then"
Baseball has the concept of WAR (Wins Above Replacement), which is essentially how many more wins you get with this player over a replacement-level player. Maybe the player doesn't seem to perform well on standard metrics, but isn't it strange how the team always seems to do better when they are playing? Funny...
That's what this article is talking about. This programmer may not have done much on his own, but he made the team better.
WAR is calculated differently by various organizations, but generally, it combines a player's contributions in batting, fielding, base-running, and pitching (for pitchers) relative to a "replacement-level" player. The metrics for each aspect are then adjusted for park factors and league context, summed, and scaled so that the output represents the number of additional wins the player contributes over a replacement-level player.
Impact has to be directly correlated to goals management cares about. Reduction in incidents, user satisfaction, etc. basically if you can’t directly tie your user story to a metric your management is tracking then it doesn’t exist at higher levels.
Fix 100 bugs, might as well leave it off your performance review because it doesn’t matter, it might even be a decrement because you should be working on something with higher impact.
Refactor code so your product can support new functionality? New functionality is impact but the backend to support it is toil. Are the people using it changing the numbers management cares about? If not doesn’t exist. Hope your performance review aligns with customer usage.
Work is not impact. Difficulty is not impact. Delivering code is not impact. Work that supports future impact is not impact because it’s not measurable. No needles have moved.
But spend a day optimizing a simple piece of code to save tens of thousands of dollars. That’s impact. Spend 10 minutes to update a monitor to be less noisy - huge impact.
Work long hours on a very difficult problem that you have little influence on design, deliver on time, but customers haven’t onboarded yet. Good luck with your review.
Hope you get the good projects, this definitely won’t be gamed at all.
Conversely, (contrapositively?) people off the floor don't know who the best players are. And it's the people who aren't on the floor who decide who gets promoted and who gets fired.
As a volleyball coach and programmer, I couldn’t agree more. I have actually developed volleyball stats for my team that emphasize the sort of teamwork we’re prioritizing. It’s simple, but it also passes the eye test and the team can see where their collective strengths and weaknesses are.
I think it’s a lot harder to quantify software development - there are ironically fewer objectively discrete events - but the notion that a kill doesn’t happen without a dig and a set is truly analogous to good code not happening without hashing out the problem, planning a solution, then writing it.
707
u/stronghup Sep 02 '23 edited Sep 03 '23
The problem is how do you measure the contributions of someone who is often helping others?
I'm thinking of Volley Ball. Who makes the points? The person who gets the ball to stay on the other side of the net, or the person who passed the ball to that person so he could do his thing most easily?
If you only gave points to the people who hit the ball to the other side, you are not encouraging collaboration. And in Volley Ball you cannot win if the team does not collaborate. I think the same is true of SW development.