Originally posted by: slsmnaz
Originally posted by: ggnl
They have people skills. They talk to the end users so the programmers don't have to.
Nope, that's the BA.
Yup.
A good PM's job is to clear problems from the BA's path. The ones that I've worked with have been reasonably good; they handle escalation to upper management (VP's and above) when their BA's run into roadblocks and they deal with vendor issues when the vendors give the BA a hard time. (I had one PM who managed to get a particularly bad vendor contact fired after I'd been screwed over one too many times by the vendor.)
Mind you, this is my experience in a multi-national corporation with over 30,000 employees in the US alone, so it may very well be different in smaller environments.
Yes the status meetings and updates seem wasteful, but they are necessary to be able to give the high-level management (VP and above) confidence in the project and thereby assure that the project keeps moving. Most BA's seem to believe that project happen in a vacuum and that as long as it gets done, everything's OK. That's simply not true. There's a massive bureaucratic and political machine that a project has to navigate through and a good PM can guide that path.
ZV