Key Resource Leaving

Unregistered says : I am serving as the PM on a software development project. Although I have some analytical and technical skills, my role is chiefly that of a PM. Another Senior technical resource was placed on the project who is more adept at software and database design. We are in the midst of a system conversion project where an in house system is being redesigned in .Net. The technical resource has been involved from the start and has been key in driving technical discussions with our client. He is also the person the client views as our chief "technical architect" on the project.

Now the Bomb Shell: I was told by executive management that this resource is leaving the company for greener pasture.

Problem: The fact that the resource is leaving is a problem, but it in itself is only part of the problem. The other side is that the company I work for is VERY small and losing a key resource like this on a project can be detrimental.

Question: What kinds of things should I as the PM do to ensure that the project doesn't fall apart in terms of things I should be asking for from executive management, how it should be handled with the client, or other items that need to be taken care of?

bas says : Yeah, that is a sh..y situation..

What me comes to mind is more of the obvious:
- make management aware of the consequences
- make sure that you as a PM can only do so much, and that the risks introduced should be addressed by management, not PM.
- make sure you have as much stuff documented (plot the guys brain down)
- make sure an account manager informs the customer and provides them with a good alternative.

Main point: make a risk assesment of the situation, write down consequences (delay, costs, etc.) for time, money and quality. Give that to your management and let them decide to take the consequences or not.

Hope this helps... i know it is not much...

Cheers
Bas

Bernard says : Has your tech. architect written a specification document to be approved by the client? Hopefully the roadmap for the project has been detailed, documented and approved...

ross_valusoft says :

Unregistered>I am serving as the PM on a software development project.

Problem: ... the resource is leaving .... I work for is VERY small and losing a key resource like this on a project can be detrimental.

Question: What kinds of things should I as the PM do to ensure that the project doesn't fall apart in terms of things I should be asking for from executive management, how it should be handled with the client, or other items that need to be taken care of?

You should have asked these questions when you developed your project plan indentifying the project constraints and assumptions and doing the risk assessment. You should be implementing the "What we do when Jack gets hit by the bus." part of the plan. And if you didn't have this part of the plan documented and approved by management, you both deserve the restless nights that will now follow. Sorry...sometimes the truth must hurt to be learned for next time.