both ? (or neither)
My fourteen year old answered it correctly. She said “yes”
Obviously, the answer is to help realize managed expectations.
And also to hit developers with a metaphorical baseball bat until they’re on schedule.
This is why I realized I don’t want to be a PM. It looks so easy when you’re not the one doing it…
There’s a difference (in reality)?
The PM doesn’t usually have any decision making powers as to the quality, scope and budget, of the overall project, so whether people’s ideas get realised is entirely down to whether they’re achievable with the resources invested.
So, my answer would be that it’s the PM’s job to see that whatever is in the agreed scope of the project gets realised, so long as it’s achievable with the available resources.
Unless I’m interviewing at a startup in which case it’s the PM’s job to enable the organisation to chase dreams, create wonder and excitement, yada yada yada…
It’s not that difficult, is it?
The PM doesn’t actually realize any ideas, but makes sure that others do what’s possible for them.
And usually, it starts off with a healthy round of “Well, this is what you want … and this is what we can do for you”
Oh how cool…you get to deal with reasonable logically people….
Your email address will not be published. Required fields are marked *
*EMAIL — Get a Gravatar
©2009-2014 Stuart Ritchie | Powered by WordPress with ComicPress
| Subscribe: RSS
| Back to Top ↑