Failing Project - unsure what to do.....and out of my depth

[BearAssCheek]

Hi - hope that no one minds me posting here. I'm reasonably new to project management, just got PRINCE2 qual last month and have a year in project admin and a further year in PMO analysis. I wondered if I could get some benefit of experience from the regulars.

We have a big project at work which is to develop a website to replace current outdated systems. It has been in train since last summer but I've only been assigned to the project for 1 day a week since January as the previous PM left at Christmas after being with the organisation for 15 years.

The deadline for delivery is aggressive - 13 weeks. I've tried to make a start with some governance, but there doesnt seem to be any interest from the project team members or the sponsor (who says, just get it done by the deadline I don't want to hear about problems).

The developers are now very tense and asking me for input on technical spec (haven't a clue as don't have a systems background) so I'm acting as a go-between to try and get answers from the stakeholders (who are shying away from committing anything to paper).

I've written to my immediate boss with a list of concerns and potential risks these might trigger. He just nods and sighs saying it will all work out - this makes me very nervous as it feels like its just me taking this seriously.

What are my options? If i go above my boss to the senior management team I'll get shot, if I don't, I'll be walking with my blindfold on to stand at the wall anyway.

Seriously considering my position at the moment and wondering if I should apply for jobs where PM is actually taken seriously. This appears to be the norm for project management at this place.

I do appreciate this is all part of the learning curve for a PM, and I really want to help but I'm getting a bit stressed at being thrown in with no support whatsoever.

Any constructive ideas at all please?

[TestMangler]

You've just described almost every project that ever existed.

I'll leave it to NLUK to tell you you're not cut out etc etc.......

[northernladuk]

Couple of things here...

1. Are you a contractor or a permie???

2. PMO+Prince != PM. You should have had something reasonable first not a big one.

3. The fact your boss is so nonchalent I am inclined to think you are making a mountain of a molehill. It is on his neck at the end of the day so he sould be taking an interest.

4. If you are permie you should be looking at some mentoring program or some form of support. Ask your boss about it.

5. Leaving is not the answer. You will be expected to devlier the moment you walk in the door if you start a new company so possibly better where you are where you can make a couple of mistakes and put it down to first time nerves.

6. Have a word with other PM's. Maybe your company doesn't follow PRINCE that tightly and they can see you are just quoting theory which doesn't instill much confidence in people.

7. Try the PRINCE or PM forums. There must be some somewhere I would have though?

8. Ask your boss for a bit more feedback. Does he really think everything is ok and the risk of failure is not that big. If so it might ease your mind and you can get on better.

[Joeman]

This appears to be the norm for project management at this place.

So likely no other projects ever get delivered on time either - you'll be fine

[TestMangler]

So likely no other projects ever get delivered on time either - you'll be fine

Well, see, you may have something there.

My current clientco is like that. Fortnightly project review meetings seem to involve the same PMs trotting out the same excuses and 'replanning before the next meeting'. Some of them have been trotting pout the same lines for the seven or so months I've been there. The techie teams consistently don't deliver and no one ever seems to be taken to task. They have bred a culture of failure and the management of failure.

[BearAssCheek]

Yer sorry forgot to add the detail.

this role is 'perm' (Fixed term) so not what you'd call 'seasoned' contractor. I asked for some development when I started, got the 'money is tight, others are in front of you in the queue' talk - ok so I did the PRINCE2 course myself cos I was genuinely interested (I don't expect to become a veteran overnight though).

I will keep asking for help and see what happens. Fair point i don't want to quit cos i'm interested - I've asked for a dedicated PM and have said I'm happy to continue to support and learn as I go along. This request was also denied, 'we don't need to involve the systems PMs'.

I did work on a previous project as an admin support and it was really well run with a great PM and a fully committed project team so I know this isn't ideal really.

see what happens i guess..

[SteelyDan]

Based on this - just got PRINCE2 qual last month and have a year in project admin and a further year in PMO analysis I'm wondering (not unkindly, so don't take it the wrong way) how you got the PM role at all? Over eager recruiter/over eager client/interview blagging?
Truth is you are a PM in theory only, and only just that.

The vital steps which you have missed out (imho - based on the info you have provided) are a couple of junior PM roles, in order to develop and learn through experience that theory is useful, but it's not the be all and end all - it's a starting point to some extent. You need experience to back it up. It's a bit like saying, I have an MBA and therefore can run UKPLC - no way.

I suspect this, together with only minimal project environment experience, has exposed your weakness(es).

If you don't get this together quickly, the team will smell your fear and see your inadequacies, and before you know it, you'll be out thru the door, with a bad rep not far behind you.

Firstly, stop panicking, take a breath, get a clear head; then identify what needs doing, by when, organise, manage & communicate with/to your resources, get them involved, and get it moving. Oh, and throw the effing P2 manual out the window. Governance can come later.

I've got to ask; did you blag your CV?

(PS. This based on you being a PM contractor)

[BearAssCheek]

No it wasn't an interview situation - in my current role (PMO Analysis) I was volunteered for 1 day a week 'Project Co-ordination' (minuting meetings, preparing risk logs, chasing actions etc.) as the previous PM left at Christmas with no identified replacement and the company wanted to keep things warm.

This has now snowballed into 'well we're not going to get any PM resource so you're 'it''. I've always been very honest about my (lack of) skills and experience, and have continually positioned this back to the original co-ordination role.

I've already started with other tasks that I CAN do such as project plan, business case etc. so am trying to make some progress..... I certainly would never have blagged the role, its way too advanced for me at this stage.....

but thanks for the suggestions, will take them on board.

[cojak]

13 weeks eh? Well you can forget Prince2 in that environment - It sounds like a PINO place (Prince In Name Only).

What you probably need is a bit of Agile project management (yes, it is out there).

Take a look at DSDM Atern - The Agile Project Delivery Framework and then go over to LinkedIn and joined the DSDM Forum group - they'll help you out with advice.

But for now go back to your requirements and prioritise them according to MoSCoW principles, then go to the developers and find out how many they've completed.

Come back and tell how you've got on.

[cojak]

Firstly, stop panicking, take a breath, get a clear head; then identify what needs doing, by when, organise, manage & communicate with/to your resources, get them involved, and get it moving. Oh, and throw the effing P2 manual out the window.

Oh yes, WSDS as well.

And if you need to run around screaming like a headless chicken - take a 5 minute break and walk to the nearest coffee shop (or at least make sure the toilets are empty before you burst into tears - I was the one in the trap. )