Project managers

Probably made it sound more innocent than it was, and it was just one example of the common behaviour of PMs. No estimate is ever good enough, they want exact time scales when you can't possibly see all pitfalls. The more complex the task the more ancy they get when you give them a figure.

And no doubt when you give them an "estimate" and go over it, it suddenly wasnt an estimate but a deadline! ( im guessing )
 
It's worse when you have a manager who asks for an estimate then writes down a different figure heheh
 
You can always 'estimate' how long it will take to satisfy a 'requirement'.

But you can NEVER 'estimate' how long it will take to 'complete' a job.

Had that drilled into me over 20 years ago and still stand by it now.
 
As a dev/designer I have no problems with project managers, in a corporate environment "I guess a couple of days" doesn't cut it, all I do is over-estimate the time scale and deliver before the deadline.
 
And no doubt when you give them an "estimate" and go over it, it suddenly wasnt an estimate but a deadline! ( im guessing )

Exactly. The point is that they want to hear what they want to hear, say anything else and they get all funny, because they can't come out and say "get it done sooner, my charts won't look right with your estimates because I didn't factor the task in correctly or allow time for unpredicted events!".
 
I should say that some are worse than others, and I'm sure the PMs on this board are very nice :)

Just sick of the snivelling rat creatures that work at my current place!
 
Lol, thought I smelled the stench of decay. So you must be one of them. If you expect developers to:

a.) Be able to read minds
b.) Be able to read the future
c.) Be your friend

then you are sadly mistaken. If a rough estimate isn't good enough for you then as I said, jog on. Here's a digit to stick in your stupid excel spreadsheet/MS Project chart/Gantt chart you sodden nose hair!

I'm not a PM, I'm just capable of looking at a task and giving a sensible estimate of how long it will take. I'm also lucky enough to have worked with project managers who don't treat this estimate as cast iron allthough I do like to deliver on time and budget. I generally find that those who bitch and moan most about PM's are those that are incapable of managing their work properly and therefore actually really need the PM in the first place.
 
I think the problem here isn't a bad PM but a bad developer. :D

I have always gotten on great with my PMs, good communication and honesty is the way to do it. Oh and always tag in some time for contingency.
 
Why are they unable to get it through their thick skulls that a developer cannot predict the fricking future and can only give a rough estimate to how long a task will take, especially when they know barely anything about the project they've just been assigned to?

The guy accepted this, and therefore asked you to review the project and required work in order to be able to give a more informed estimate. Why the issue with this? That's standard practice the world over no matter what kind of manager you are dealing with.

Why are you unable perform a simple task like estimate how long a required item of work will take anyway? Extremely inexperienced, or just a bit ****?
 
The guy accepted this, and therefore asked you to review the project and required work in order to be able to give a more informed estimate. Why the issue with this? That's standard practice the world over no matter what kind of manager you are dealing with.

Why are you unable perform a simple task like estimate how long a required item of work will take anyway? Extremely inexperienced, or just a bit ****?

Are you blind? I gave an estimate, which obviously wasn't what the PM wanted. So they ask me to go away and look into it to give them another one.

Bear in mind we are not talking about a week or more's worth of work, it's a few days. It is impossible to be more precise unless you DO THE BLOODY task and them tell them how long it took. I am not in a position to make a more informed estimate as I am not a developer on that project.

Jesus, what is so difficult to grasp here? Any decent PM here would realise that you can't bring a developer onto the team and expect cast iron predictions from them, you can try but be it on your head if things turn out differently.
 
I always over estimate to a safe margin, seems to work

Exactly what I always do. If BY GODS GRACE I doget a decent PM, I'll obviously explain in more detail how my estimate is formed and how decent an estimate it is, but this usually just confuses bad PMs, they want a number, and the specific number that they are thinking of, and nothing else.
 
There comes a point when spending more time trying to decide how long a small task will take, will take longer than the task itself. The problem is the unknowns.
 
Mr problem was your use of Guess in the OP. The PM asked you to spend more time looking at the elements and move from a 'guess' to an estimation.

Seems perfectly reasonable to me.
 
There comes a point when spending more time trying to decide how long a small task will take, will take longer than the task itself. The problem is the unknowns.

Then there's also the point where moaning about the task exceeds the time taken to conduct the task itself.
 
It's all about perseverance/analysis really, I'd ask him/her a time that would be reasonable in the foreseeable future and then perhaps giving him/her a rough estimate around his/her expectancies.
 
Back
Top Bottom