Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API

From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "estimation"
-
Scrum Master: Let's estimate the task. Chose your estimations individually, then we will reveal at the same time and discuss
- variety of votes, ranging from 1 to 8
Product Owner: I don't agree, this should be a 1 or 2.
Dev Team Lead: Agreed, this is why I chose 2. Let's vote again.
- All votes now are 1s or 2s
Good fucking job 🤨11 -
Super trivial but who ships a laptop to a new employee with random software on that is clearly for their own preferences? I don't use classic shell, I don't like classic shell, and it hugely fucked with both my opinion of the new place (an IT company, ffs) and my estimation of the person who configured it. Do whatever shit you must on your own machine but get out of my way and let me use the fucking os without more pointless shit! I wouldn't do this to you, no matter how much I might love some obscure additional layer for primarily nostalgic reasons. Raging!7
-
One thing that I've noticed is that devs are the most stupid human beings while doing estimation or planning for the sprint. And I'm a dev too2
-
"Fast" random-number/sample based estimation of logarithms:
https://pastebin.com/niVB57Ay
The result of rAvg(p) is usually "pretty close" to log(p)/2
rAvg(p, 1000) seems to be the golden number. 100 is a little low, but I've already pasted the code. Eh.
Don't know why it works, or if average results are actually considered "close" for logarithms of e.7 -
I don't care about God's existence but somehow I'm meeting the deadlines always. It's a new thing for me.
I have stopped paying attention to my work due to interviews and somehow my work performance is getting better and better each day.
All I needed was to work less and give estimation according my mood each day.8 -
When freelancing, do you charge for estimations?
Situation is that I'm a sole android developer (4 years experience) and each time I encounter some agency or a client I feel like I'm between a rock and hard place.
Some of the clients come with ready with list of requirements and ready backend/design sketch and they want me to give them a rough estimate.
It's as if they expect me to take only 2-3 hours for estimation and that's it. But actually this was the second time where I had to spend around 10 hours investigating everything so I would be able to give a half decent estimation at least.
This particular client's project turned out to be a mess and I had to spend 10+ hours to estimate only 70% of his project. I asked him if he would be able to pay under a reduced tarrif and the client was shocked, started doubting my competence level and so on.
In the end I gave him a rough 400 hours estimate and he started complaining that others estimated only 200 hours for his project. So in the end I just wasted my time.
Now it's my bad that I voluntarely invested too much time in this estimate without notifying client prior that I might ask to pay for estimation, next time I will try to do this ahead of time.
It feels like only big agencies who have free resources have a competetive edge against sole freelancers, it really sucks wasting so much time to estimate half baked requirements and assets. Also most of these clients and agencies are purely lazy and most of the time they don't even plan signing, all they need is someone to estimate their work for them.
I'm thinking of starting to charge for estimations and communications in a form of consultations. Is that a good idea?8 -
I just do the Three-point estimation method: It's easy enough to remember and somewhat scientific: https://en.wikipedia.org/wiki/...
I made a spreadsheet a while back which serves as a template. I guess nowadays there must be at least one website with a fancy diagram no doubt..1 -
How do you guys actually estimate any given task..?? What do you consider..?? Or do you just guess it as per experience..??7
-
* break it into elementary steps, small enough to fit into your "estimation time unit", e.g. days or hours.
* estimate those steps for "developing at a leisurely pace" if nothing goes wrong.
* think about "what could go wrong" (list everything!) and adjust values accordingly.
* adjust total amount with experience values, like:
* times 1.2 for every manager
* times 1 to 4 based on which legacy projects i have to touch
and finally:
* multiply with `1+log(t/u,2)`, with `u` being the amount of useful data in the requirement description and `t` being the total amount of data in the requirement description
* sample: with our current "favourite" customer, about 90% of all tickets is garbage, so t/u = 100/10 = 10 => log(10,2) = 3.3 => multiply everything with 4.32 -
Ugh, I finally got a big project at work as the main backender but I still have a lot to learn. I fucked up the estimation for a big component and this is the fifth night im working late because I feel responsible.
Fuck this shit.4