|
Here is my perspective, as a product manager at a large (Fortune 500) corporation for the past two years... I don't know how to code (well, anyway...), but I try to take care of the dirty work so that the development team can focus on doing, you know, development. This means figuring out the flow of transactions (we work with web services, and expose our own web services to clients), field level details, managing the intake of feature requests, figuring out why certain things are broken or behaving in unexpected ways... Basically, I move all around to make sure the developers are able to focus on they are able to do, and protect them from the headaches that upper management and business sponsors produce. I try and manage the goals of business asks and user experience with the abilities of our development team. If there is a major change in design or scope, I make sure to consult with the development lead before I commit to anything. I don't assume to be more important than any developer, or that I know more than them. I understand what my role in the organization, and my relationship to the development team, and I know who is doing the work that makes us all look good. I don't know if this satisfies any developers who read this, but this is what I come into work trying to accomplish. |