Project managers

You really have no clue what he is on about otherwise you would have more of a grasp on what he is talking about and not reffer to him as "a spanner". I suggest you be silent as ironic as it is, it is you that cant talk to someone that you feel is below you with a narrow minded attitude like that.

Cheers codec, it seems there are a few too many people in here that have quite obviously missed the point or are far too quick to jump to uninformed opinions - sound like perfect PM material, hyuk huck! :D
 
What other kind of opinions were you expecting, given that this is the internet and we can only go by what we deduce from the limited information provided?

Well for one I didn't expect so many people making such blatant accusations about competancy, etc considering this was obviously a rant thread and I gave brealy any details to the context.

Considering the amount of PMs in this thread (whether they admit it or not) and the "oh you don't sound like th kind of person I would want to work with" comments, they certainly never fail to live up to their reputation. :)
 
fella, you do yourself no favours!
You missed the mark, you were too quick to jump to an uninformed opinion.
You also still seem like the sort of person most people on a project would want to avoid.

I love the fact that people on here are banding accusations around, when the only accusation I can be held guilty to the mob that is the OCUK poster is not providing enough detail. Still, I wouldn't expect a PM to know the difference. :p
 
To be fair, it is mostly you doing that.

You are treating all PM's as if they are idiots just because you've had a bad experience and/or not really understood what the PM was telling you.

There are plenty of good PM's around, don't assume they're all as bad as the worst one you've had.

Sigh. If you'd actually read the thread you would have discovered that I HAVE said that there are good PMs, and there is nothing more I like better than working with a good PM. Unfortunately, most PMs I've worked with have not been good. That is my experience, so deal with it.
 
I'm not a PM, but I recognise that one bad PM doesn't make all other PMs automatically bad.

I once had a bad curry but I dont bitch and moan that all curry's are bad.

Currys are not PMs!

Honestly, you may think I'm being beligerant but from every developer I've ever spoken to, they have worked with far more bad PMs than good ones. It's the nature of the role, you don't need any real qualifications to do it and the fact that you can earn a decent wage draws in all sorts. Unfortuantely, a lot of people who clearly won't make good PMs get hired. Probably due to the fact that the demand far outstrips the supply of good PMs, and it's very difficult to judge a good PM in an interview.

This obviously doesn't happen with devs as they need to have proven technical qualifications and experience, and if you can't do the job it's a lot harder to justify than if you were a PM.

This could also be why every UK government IT project ever started has run ridiculously over budget and often the spec is completely unfit for purpose. :)
 
Last edited:
That case fancy filling in some of the details, such as your age, length of time in your current role, amount of time/experience in the industry, size of company you work for, amount of people involved with this project, how many other people in this project are dependent/affected by your deliverables?

Why would I bother, as has been said NUMEROUS times already, this is a RANT thread. Why is this so hard for people to grasp? Being that it is a RANT thread, I would expect anyone with half a brain to recognise this (clue: angry smiley as thread icon) and realise that I may not be providing all the details, so probably not the best basis to form an opinion of my competancy...

You keep throwing up what comes across as very childish remarks about PMs and how they are all the same, it makes any valid points you may have hard believe.

I'm not trying to convince anyone, but clearly there are people in this thread who understand what I'm talking about.
 
A PM is only the co-ordinator, he can only work with what is feedback to him from all the parties involved. Crap in crap out.

So if he has some little Dev with a chip on his shoulder unwilling to provide useful estimates then I can fully understand why lots of projects run over budget/schedule.

Little devs with chips on their shoulders don't last very long. Crap PMs do. Go figure.
 
If you're going to make wild accusations about PM's you really need some sort of detail for your argument to be seen as valid.

If I started a thread stating that I hated all developers as they can never appreciate the need to manage time and give me guesses on how long taks will take - would you expect all the replies to be yeah fair enough I agree? No, I'd get developers in there stating that what I was saying was rubbish and my experience clearly does not represent the general opinion.

This isn't about forming a general consensus of the quality of the average PM, it's a rant thread! I don't expect anyone who doesn't have the same opinion as me to see it as valid, and I'm not trying to convince them!

It seems to me that many people here have unnecessarily taken these comments personally, and to those people, if they are not PMs, I would have to wonder why.

How many rant threads do you see on OCUK? Do you feel the need to weigh out the pros and cons of the stated opinion in those threads?

So, repeat after me: "He's just ranting, he's just ranting, he's just ranting, he's just ranting, he's just ranting, he's just ranting, he's just ranting..."
 
Judging by this thread, PM's earn every penny for having to deal with IT 'tards who believe their work is an artform rather than simply a means of getting something done, to a certain specification, within a budget.

Much akin to IT support moaning that people don't understand PCs and go to them with petty problems - generally because people couldn't give a crap about how long you've been building computers, how 'any n00b' knows how to do something, how things are so 'obvious', they just want the thing on their desk to do what it's supposed to do so they can get on with their job :p

Not the same thing at all. Devs need good PMs, and crap ones do nothing but make our lives a misery. It's got nothing to do with arrogance or a lack of understanding, it's all about meeting your responsibilities and doing your job well, something that most PMs I have worked with know nothing about.
 
You seemed to have described yourself perfectly.

Just because someone doesn't agree with you, doesn't make them uninformed.

Are you really this ignorant or just doing it to amuse me?

You are uninformed because you know nothing about me or my situation. The only thing you know is that I had a rant, if you think this is enough information for you to make character assessments then please do go on, your making yourself look like the village idiot is quite amusing! :p
 
Sorry my mistake.

But don't call me stupid. You don't klnow enough about me or my siuation to call me stupid (sound familiar?)

I apologise, I'm just getting pretty tired of having to repeat myself to you because you seem determined to not read what I'm posting.
 
I didn't look at the correct job - one mistake.

I still stand by all my other comments.

If you don't agree with them, fine, but they are not misinformed.

Obviously you know nothing about me so any accusation you make against my competancy is irrelevant, but I suppose you are entitled to your opinions.

You seem to have taken this whole thing quite personally. You are a PM, right? I can't remember if you denied it earlier.
 
At least this is the impression I get from a 'non-IT' professional role where things like giving accurate estimates and working to set budgets and deadlines is far from an outrageous request but rather an absolute necessity :p

In the industries I've worked in, I've never seen a dev who was unhelpful towards the project, though some are more pro active than others. It tends to be that devs manage the micro project that is their task set and communicate to the PM how long it will take and regular progress. It is the PMs job to make sure everyone has what they need to do the work and resources are booked in time. If the project fails in a professional organisation, it is rarely (if ever) because a dev had a chip on their shoulder, you just can't get away with it.
 
Back
Top Bottom