975
Task estimation
(lemmy.dbzer0.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 16 Sep 2024
975 points (99.2% liked)
Programmer Humor
19623 readers
1 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
founded 1 year ago
MODERATORS
A typical project manager will get a range, take the lower bound and communicate it as the only relevant number to every other stakeholder. When that inevitably does not work out, all the blame will be passed on to you unfiltered.
Depending on where you work it may or may not be worth giving someone new the benefit of the doubt, but in general it is safer to only ever talk about the upper bound and add some padding.
I hear this criticism all the time, but I've never seen it happen in 5 companies I've worked for so far. Usually there's an understanding that estimates are wild guessing, and things are planned using dependencies rather than timeliness.
Only novice PMs do that and believe it or not, the project manager carries the can for failure .
I have a friend who's a new PM (in scaled agile). He isn't up on expectation management.
We have a process where we request data from another agency which takes "from 7 seconds to 12 days"
And of course he tells people that. And of course they hear "7 seconds"
I have told him that if the SLA is 12 days, say "less than 12 days"