I totall agree with what you are saying. Unfortunately, my job is such that I am project manager and lead programmer (sometimes lead = only) on most projects. I have a manager, but his ability to "Project Manage" equates to "How's such-and-such coming along?" He is not only terrified of actual project management, he has said, point blank, that he isn't going to do it. Which leaves each of us to manage our our projects. A sad state of affairs, but there isn't anyone here on the management team who actually KNOWS how to project manage when it comes to software. Alhough I do, I would hardly want to raise my hand for the job, as when a strong manager comes in and a good process implemented, a BUNCH of people are going to get pissed off because they actually have to invest time of their own in the software they want developed.

The development cycle is the responsibility of everyone involved. PM, developer and customer, and each has a stake in it. Part of a good PM's job involves helping the customer to see their stake in the project, get them to have some kind of pride of ownership in the project, and motivate them into being a part of the solution, rather than just the person who is asking for the code.

What I wouldn't give for someone to be the point man for my projects, interfacing with the L-Users and allowing me to do what I do best, that is, write code. Until that day comes, I'll have to dress business casual, instead of jeans and my "RTFM" T-Shirt, work 8-5 - maintaining my hours of "Seat Time", be nice, smile pretty, and watch my back.

C-.