Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
millenialdev33610d8. Once finished. Back to step 1.
Wack657110dHave you considered actually getting a dart bord, hang it up and the next the fuckers ask for an estimate tell them to come to your place, gatter all the devs there too and just ask them to throw the fucking darts themself, as you devs are getting to good and only aim for the 20 points slice... (Every dev has to be in it of course and acct, like they do it all the time... (Sure you might get fired, but probably it will be wort the laught ;))
T-shirt size estimates only work if you are basing those on collected examples. Best way I found so far was taking tasks that are done and write down with the team what was done in the task. Than I search one smaller and one greater task and do the same. Afterwards I name them S M L.
Really important is here to never tell the team the time it really took because those numbers will stick and they stay always with wild guesses.
Every two sprints with 2 weeks (if you do sprints) take some new tasks and do the same again.
Estimations should then be only done by comparing the task to estimate with the 3 samples. And let the team discuss where they see the task. Is it smaller than S? Like S? more than M? but less than L?
When you don't tell the team the numbers behind the sizes you get a pretty good estimation most of the time.
d4ng3r0u5429410dMy boss has suggested this to help me with estimating (as I'm not great at it).
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job