News for hackers. Stuff that matters.
Re:Rules of Thumb for Software Development Estimations by SanderNL on Wednesday May 03, 2023 @06:16AM (#35800365)
So your team does basically, let’s say, 10 gold stars a week.

Your epic and VeryNecessaryFeature(c) takes 30 gold stars.

Pointy hair boss: this takes 3 weeks. (and make it 2)

How is this different from skipping the proxy and just using time directly?

Re:Rules of Thumb for Software Development Estimations by tbrake on Wednesday May 03, 2023 @06:22AM (#35800415)
The answer is not having a PHB.

No non-unit-of-time estimation system will matter if there isn't buy-in from all levels. If the Directors/VPs/C-Suite etc view development in assembly line terms, then Xpoints = Ytime can never be avoided and yes, it just becomes an exercise in frustration.

To date I haven't found a good antidote other than avoiding workplaces that view estimations as exactimations of time.

Re:Rules of Thumb for Software Development Estimations by Ensorceled on Wednesday May 03, 2023 @06:45AM (#35800619)
Ah, so the best way to provide time estimates so that the rest of the business can do planning is to not work at a business that needs to do planning.
Re:Rules of Thumb for Software Development Estimations by tbrake on Wednesday May 03, 2023 @07:20AM (#35800945)
On a story by story basis saying points=time is an idea as silly as your deliberate misinterpretation of my post, yes.
Re:Rules of Thumb for Software Development Estimations by konschubert on Wednesday May 03, 2023 @06:23AM (#35800431)
It’s different because it can remove a bias out of estimations.
Re:Rules of Thumb for Software Development Estimations by SanderNL on Wednesday May 03, 2023 @06:45AM (#35800617)
But eventually everyone knows that your gold stars stand for weeks. So how does this help?
Re:Rules of Thumb for Software Development Estimations by konschubert on Wednesday May 03, 2023 @06:53AM (#35800699)
Because you can keep tracking how long things actually take. And then divide by the gold stars, to see how much time you actually need for a golf star.

And that number might change over time and that’s okay, and you can keep tracking it.

It’s a bit of a mind trick.

Instead of thinking: “How long will this ticket take?” you think: “Is this rather as complex as the 3 star tickets I did in the past, or is it as complex as the 5 star tickets? “

You estimate in terms of other tickets, not in terms of time.

It helps to remove bias.

Re:Rules of Thumb for Software Development Estimations by SanderNL on Wednesday May 03, 2023 @07:40AM (#35801130)
The only quasi-interesting property this has is that it can change over time.

Nothing you said changes the main problem: gold stars are weeks and we all know it. Next year they are two weeks, fine.

Re:Rules of Thumb for Software Development Estimations by bluefirebrand on Wednesday May 03, 2023 @09:14AM (#35801994)
"You said it would take a week"

"No I said it was 12 jellybeans"

"but we all know that 12 jellybeans is a week!!"

"No, we all know that 12 jellybeans is explicitly not a week. It just happens that 12 jellybeans has taken 'around a week' in the past. An estimate of 12 jellybeans is still not a promise that it will only take a week."

Re:Rules of Thumb for Software Development Estimations by chasd00 on Wednesday May 03, 2023 @03:01PM (#35806328)
then "ok, well i'm not paying you until what i asked for is in production".
Re:Rules of Thumb for Software Development Estimations by bluefirebrand on Wednesday May 03, 2023 @03:05PM (#35806378)
Withholding salaries is a crime, so... I strongly doubt it.
Re:Rules of Thumb for Software Development Estimations by Izkata on Wednesday May 03, 2023 @10:00AM (#35802495)
This mapping falls apart when the individual devs have different levels of experience. A gold star is a different unit of time per individual; Dev A might be able to complete 1 gold star in 1 week, but Dev B with less experience takes 2 weeks.

The right thing to do isn't to estimate the average 1.5 weeks, since the case might not actually be done for another month, and it might end up actually being done by Dev C who just joined the team, for who 1 gold star is currently 3 or 4 weeks.

Re:Rules of Thumb for Software Development Estimations by konschubert on Wednesday May 03, 2023 @12:28PM (#35804337)
A team has an average.
Re:Rules of Thumb for Software Development Estimations by willcipriano on Wednesday May 03, 2023 @12:40PM (#35804494)
If you took all the winning lottery numbers you could probably find a average as well.
Re:Rules of Thumb for Software Development Estimations by konschubert on Thursday May 04, 2023 @03:01PM (#35820454)
This is a nonsensical response. An absolute non sequitur
Re:Rules of Thumb for Software Development Estimations by ohthehugemanate on Wednesday May 03, 2023 @10:49AM (#35803080)
No, they are not weeks, and the minute "we all know it" you are fucked.

Engineers are not concerned with time. They are concerned with feature completeness and quality. They do not care how long a task takes, only that it is done Right. When the PM asks how hard it is, that's their only consideration.

The PM only cares about time to make accurate predictions for the rest of the business. A given task takes as long as it takes to be done Right. If the business wants it on a different timeline, the business has to redefine the task, or redefine Right (ie skipping tests or doco).

Research bears it out: human brains suck at estimating time, and are much better as soon as you talk in terms of effort.

BUT if you want to insist on brute forcing through our cognitive biases, I have good news: you can do almost as well by tracking the relationship between "developer time" and "real time". You're still dealing in abstracted units, of course, but you can still pretend you aren't, which is the important thing.

Re:Rules of Thumb for Software Development Estimations by SanderNL on Wednesday May 03, 2023 @11:02AM (#35803223)
I get the sentiment, but ultimately business is time-bound. Everything is about time. But now we have a bunch of “engineers” (that somehow are fundamentally incapable of structured planning and execution) that are “not concerned with time”.

I found your characterization of engineers and PMs not useful and a bit childish. This is not how money is made.

Let’s just agree I don’t understand this. You sound well-informed and I’m just a simpleton.

Re:Rules of Thumb for Software Development Estimations by ohthehugemanate on Wednesday May 03, 2023 @10:43AM (#35802993)
The problem in your story is a non technical boss making time estimates/demands. If that's gonna happen, the developers shouldn't bother with estimates at all because no one is listening. They can just go on missing the boss's fantasyland deadlines and save themselves the trouble.

If the boss wants to know how long things will take, they have to ask the engineering teams. And the most accurate way for an engineering team to answer is with a track record of abstracted unit estimations and how long they took, to predict how long the abstracted unit estimation in question will take.

And when the PHB says "make it two", the engineers can only reply "ok, tell us what features or standards to cut." No different than wiring a house: we can finish faster if you choose some rooms to skip, or some safety standards to skip. But those are the boss's decisions, not the engineers.

BTW I agree with the responder who says quit from those environments ASAP. I don't know how engineers can overcome a dysfunctional business lead like that... and that kind of business lead is often an expert at making sure the repercussions land on someone else. Case in point, by asking you to finish faster he is tacitly asking you to skip capabilities or safety checks... and that way you're responsible for the fallout.