Got to switch HTML guys mid-stream

Question

So, this is my first PM experience and shame on me if I'm not learning something new every day. The guy I hired to do my XHTML/CSS accepted a full time position somewhere else. Which SUCKS.

I can either stay with him (he said he could get a friend to help during this transition) but he HASN'T been dependable. However, if I switch horses at this point I would have to get a new CSS, new master page, half my pages would have the old one and half the new.

UGH... really stinks. Any recommendations from people that have done this before?

Oh, and PS, I need all of this done, like, three weeks ago.

UPDATE: Sorry, I wasn't clear, this isn't an internal hire, I was sending my compensation to a company that was doing it. This is why I am concerned that the new company won't want to work with the old company's stuff.

Answer 1

Why would you need to get new CSS etc? Is the code that bad that it would need throwing away? CSS shouldn't be that hard for someone to pick up - especially if you can hire a new guy quickly enough to get a shared transition period.

Answer 2

Get a new person in, and look for someone that has experience using and extending someone elses code. Halfway through a project isn't a good time to be rewriting already existing code, and it also isn't worthwhile trying to depend on an undependable resource (i.e. your ex-developer).

And see about getting your deadlines extended ;) Also, risk assessments of future projects should include as a risk that your developers could change jobs mid-project and factor that in. If they don't your deadlines get met and you get good rep. If they do, your deadlines still get met because you anticipated this and you still get good rep :)

Answer 3

yeah, but usually these guys like doing their own... do you think a new guy would use one from the old guy? I mean it's a great format.

Also, I know this isn't the format for this but if anyone has someone they could reccomend in the NY metro area that can get good work done fast I'd love an email.

Thank you.

Answer 4

Dropping in a new HTML hire shouldn't be too difficult if you have all the source code and a documented remit of what needs done?

At the end of the day you should always have some kind of contingency plan just in case your employees choose to walk out in front of a bus one day.

Answer 5

As the project manager, it is your decision to make whether they should "do their own" or work on the existing code, not the programmers'. If you are to be an effective PM, it doesn't matter what they like or what they want; you must make the decision.

Answer 6

Developing on existing XHTML/CSS codes should not be any problem at all. Picking up the codes should take only a few minutes.

Your best option is to find a catcher and get things rolling. As the new developer work on the code, setup an appointment with the previous coder to explain any parts of the code if necessary.

There should be no need for a new CSS, masterpage and whatsoever unless the original one is plain horrible.

Answer 7

Working with someone elses code shouldn't matter, sure, it's always nice to be able to work on your own code rather than someone elses, but it should only be a matter of a half hour to an hour (depending on the size) to figure everything out.

I do plenty of work on websites that were started by someone else, its part of the job and a company that won't accept that isn't worth dealing with in my opinion. The only good reason, as has been said, for not working with someone elses XHTML/CSS/masterpages etc is if they are simply shocking or don't work properly and it would be quicker to start from scratch than try to fix.

As the project manager, it's ultimately your decision to decide what gets done, so take the advice of another company on the existing code as to whether it is decent or not and then make your decision. Granted if you want, I'll have a quick look at it and give you my opinion on it to give you a view from an unbiased party.

Good luck! Don't be pushed into a decision you don't think is right.

Answer 8

Don't Panic.

People come and go all the time, it is OK. As the project manager you have to focus on two things:

1) Protect any investement made by project stakeholders so far.

2) Manage the change. Change is going to happen whether you like it or not, your job is to make it happen in a managed manner.

To protect the investment you need to:

• plan and organise the audit of work done so far,

• make sure some state of completeness achieved, i.e. task can be handed over;

• arrange a replacement for the guy,

• make arrangements for knowledge transfer,

• negotiate arrangements with the current guy in case his help is going to be needed in the future.

To manage the change:

• let everyone involved or affected aware that the guy is leaving,

• let everyone constribute to a prioritised list of outstanding tasks currect guy is expected to complete before he leaves,

• re-negotiate deadlines, scope, quality, budget as required,

• re-negotiate any project dependancies,

• as a last resort you might consider the option of scrapping the project.