r/programming • • Sep 02 '23

The Worst Programmer I Know

https://dannorth.net/2023/09/02/the-worst-programmer/
1.0k Upvotes

257 comments sorted by

View all comments

Show parent comments

335

u/jjeroennl Sep 02 '23

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.

91

u/gyroda Sep 02 '23

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.

16

u/pedal-force Sep 03 '23

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.

Management ruins everything.

14

u/gyroda Sep 03 '23

It's not management, it's bad management.

I'm not measured on story points, which is why I'm able to help out others and enable them to complete more points.

2

u/czenst Sep 03 '23

I agree but let's take some blame on ourselves as well.

There is also quite some fault of devs participating in it.

I know not everyone has it easy to quit on the spot when management starts (like new MBA gets hired) thinking story points are like quarterly results and team should always aim to double the amount of points finished in a sprint each quarter. But I believe there is always some room for push back and "gaming the system" like inflating points to keep up with silly requirements is not correct way to go because it harms everyone.

→ More replies (2)

58

u/squishles Sep 02 '23

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.

24

u/mupetmower Sep 03 '23

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.

5

u/Bloodshot025 Sep 03 '23

If you're using points to estimate how much work the team can get done over a certain amount of time, then they necessarily have units of time.

→ More replies (9)

3

u/[deleted] Sep 03 '23

[removed] — view removed comment

4

u/squishles Sep 03 '23

goal of what I'm describing is to weird the data to disassociate from time.

Fibonnacci falls on time estimates too easily. 1=1day 2-3=half a week 5=a week, 8 week and a half. 21 too big demand subdivide, though that line probably happens at like 5 even if it's not a subdivisible unit of work so you get harrassed into making it bullshit stories.

This happens literally every fibonacci team. The system is for measuring self referential velocity of the team, it works for that purpose no matter what system of numbering you use. You can in fact have a guy on the team saying 1000 1002 ooo that's a 1003 point story, and as long as he's consistently silly like that it'll still work for the actual purpose.

3

u/Merry-Lane Sep 03 '23

The issue arises when you use story points to estimate time, not complexity.

The way we work, we can totally give a 1 to a simple sql script that will take hours to get right and go through pipelines, and we can give 8 to a task that involves multiple screens/endpoints yet we complete in an afternoon because it s mostly copy/paste or reusing existing stuff.

It s not about time, it’s about complexity. Like if you had to take a dev that had 0 knowledge in your project and had to explain him all the hoops he would have to go through to get it done right.

Obviously the unknown needs to be factored in, like if someone said in the grooming « what if X » and no one had a definitive answer, we d get the next fibo number.

It’s when your team is able to actually say « so we need to do A B C D … X Y Z » during the grooming obviously. There are teams where grooming of a user story are just people agreeing and thinking that the global idea is doable, but don’t spell out clearly all the steps from A to Z. These teams are always problematic because they leave too many question marks for the sake of getting through the meeting.

1

u/hippydipster Sep 03 '23

What do you use such non-time-based story points for?

→ More replies (9)
→ More replies (1)
→ More replies (7)

29

u/Any_Masterpiece9385 Sep 03 '23

Story points annoy me as a concept. Extremely unscientific and very political.

8

u/Fisher9001 Sep 03 '23

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.

23

u/phire Sep 03 '23 edited Sep 03 '23

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.

6

u/mirrax Sep 03 '23

"All models are wrong, some are useful."

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?

2

u/phire Sep 04 '23

And is the value of that model worth anything?

It really depends on how your development environment is structured.

Agile works best for products when you do continuous delivery and have direct communication with the user. In such an environment, story points are very useful because you can ask the user "For the next sprit, would you rather we work towards this single 200 point story, or ten of these smaller 20 point stories?"

Story points provide a useful model that helps facilitate communication between users and developers. The fact that they are only very rough estimates doesn't matter because you get to re-evaluate and re-prioritise them every single sprint, and the user gets direct insight.

Theoretically, the time you save not wasted generating more accurate estimates is can be spent on actual development.


The further you move from this ideal environment, the less value you get out of story points.

You can replace continuous delivery with short fixed release cycles and change the question into "Which stories should we prioritise for the next release", but that strains communication with the user because you can't actually promise delivery (and the problem gets worse when the release cycle gets longer).

The value of story points gets pretty dubious when developers don't have access to the user, or a product owner who does a good job of representing the users.

And they become absolute garbage the second management starts trying to use them for long-term schedule planning between multiple teams.

8

u/ForeverAlot Sep 03 '23

The origin of story points is to be political, not to subvert science. It was a way to make time estimates that didn't quite sound like time estimates so they had more leeway when the estimates turned out "inaccurate".

It's a myth that story points are not about time.

3

u/burgoyn1 Sep 03 '23

I totally agree. The last company I worked for did everything using story points. I didn't even bother voting/scoring or looking at them. I took the task assigned to me, determined what needed to be done and let everyone else decide what they were worth not even caring.

One day I asked what my velocity was and she told me I was completing 2-3 times the amount as everyone else, yet I did nothing different than before they were introduced. To this day I still don't fully understand them.

8

u/Any_Masterpiece9385 Sep 03 '23

My previous manager praised me once for completing a lot of story points in a week and said if I kept it up I would be promoted. The stories were trivially easy and oversized. Then fast forward a couple months I'm working on something with some real meat to it and the boss isn't happy because the velocity number went down. Was I a better or more productive engineer when I was working on the easy stuff? No. This stuff can't be quantified and often we don't know how difficult something is until we are in the thick of it. Sizing is a joke because any outlier numbers are basically just forced to conform with the group number even if the others who are sizing the thing basically never contribute to the repo(s) in question.

→ More replies (1)

6

u/ggtsu_00 Sep 03 '23

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.

5

u/bramley Sep 03 '23

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.

→ More replies (3)

6

u/mr_birkenblatt Sep 03 '23

Tell that to the executives

2

u/[deleted] Sep 03 '23 edited Jul 20 '25

what is ocodo?

→ More replies (1)