61–70 of 178 posts
Want to get a higher salary? Do yourself and a broader programming community a service.
Learn to negotiate! Learn to negotiate! Learn to negotiate!
My PM is on vacation this week and I've had to partially fill in. I have been getting frantic urgent emails from roughly 7 am till 1 am. If this is what the guy puts up with, he deserves a couple bucks.
This sort of approach is not limited to coding at all. It does require that you have some control over the issues that take up your time and energy. If your PM were to quit and you were to take up that position, I'd advise you to take an in-depth look at removing the problems that lead to frantic, urgent requests.
Earlier quoted context omitted.
I crossed over from Project Management into Engineering, and my experience was that as a PM my job was to be bothered from Sunup til Sundown and periodically in between. I was expected to know everything about anything that I was asked about, and I was responsible for a large number of people's output without having any authority over them. It was horrible. I think the issue with the SO question is simply the view th…
What you describe is a dysfunctional organization, not a justification for PMs.
if the film crew \ theory x idea is right then an org aisation that is becoming dysfunctional hires more PMs
I suspect that they are symptom initially and then cause.
The easy answer is: because that is what the market dictates. Programming may be difficult, but I'd be willing to bet there are a lot more programmers out there than people willing to be a PM (and stick with it).
1 BA/PM generally spend most of their time dealing with politics, governance and bureaucracy.
2 BA/PM spend a lot of time trying to elicit requirements and deal with scope creep.
3 BA/PM act as a conduit between parties and stakeholders who rarely agree. They attempt to gain compromise and keep the show on the road.
4 BA/PM take some risk and responsibility for things going wrong. And need to fix these things.
5 BA/PM act a managers, managing people, strategy, finances.
There are more but you get the context. There are lots of intangibles (or BS) needed to manage a project. You need someone to deal with it.
In certain industries BA/PM with a mixture of business, technology and BA/PM skills can demand more pay.
I was a doubter before but seeing the daily issues that come out on a challenging project, these BA/PM are probably underpaid.
Earlier quoted context omitted.
Honestly, I don't think it is a useful or thought provoking question. As numerous people have pointed out, the entire premise is false. Intentionally or not, it's basically trolling for "programmers are great too!" type comments.
> Intentionally or not, it's basically trolling for "programmers are great too!" type comments. Wow, this is not true at all . Just because you don't see the question as useful doesn't mean it isn't. As an entrepreneur (and a programmer), I am genuinely curious about the situation. We don't pay our PMs as much as we pay our programmers. Does this mean we're doing something wrong? Did we decide this because of our tec…
I view the PM role akin the role a sweeper plays in curling. A good PM will clear the path for others on the team to do what they do best. Sometimes that's wrangling with devops so the developers can keep programming, or it's calling a meeting with stakeholders to brief them on potential issues before they get out of control. A good PM is offensive, not reactive and thats why a lot of times it seems like they're just…
Just a tip, if you want to keep with your sports metaphors, and meant to say "a good PM is on the offensive", you probably meant "a good PM is proactive (acts to solve a problem before it shows up)". Describing someone as 'offensive' is saying there is something about them that offends you.
I can tell you that I have worked in 4 major roles: - engineer - sales engineer - business development - CEO
In my experience, the pay is directly tied to the need of the position to manage uncertainty and ambiguity, and evaluate difficult risk/reward tradeoffs. As you move up the hierarchy, you do more of this.