Project Management

Please login or join to subscribe to this thread

Resource Transition Plan

linkedin twitter facebook  
avatar
Anonymous
Has anyone got a plan in MS Project for resource transition? We have a team of 13 people in UK. The plan is to release 8 people, move the remaining 5 to India and recruit 8 new people in India to take over from the released resources. The resources returning to India will do the transition to all the members. Moreover, some lead resources will go to the UK office and get a lead-level knowledge transfer from the UK staff (which is about to be released). We are working against a deadline and have only 4 months for the entire project.
Sort By:
avatar
Dave Garrett
PMI Team Member
Senior Advisor to the CEO| PMI Sterling, Va, United States
Hi Anon,


Here are a few quick tips and tricks from gantthead's "Change HEADWAY" process to be used when planning any significant change.


Tips and Tricks

- Include Preparation Activities. Include activities that speak to preparing for the change, to understanding the why and the what, and to helping people consider the impacts on them, those around them, and also the impact on the organization as a whole.

- Include “Letting Go” Activities. Include activities that speak to letting go of the old way and celebration of this.

- Include Adoption Activities. Include activities that support people while they are adapting to the new way of doing business.

- Include Celebration Activities. Include activities that celebrate the anchoring of the way we do business after the change is complete.

- Include Hand-Off Activities. Include activities to hand-off the project results to operations.

- Consider Exit Activities. Depending on the degree of change being introduced to the organization via the project, it may be important to consider activities that allow people to exit the organization. This goes a long way to helping the people who chose to remain with the company feel more comfortable about how the organization is managing the more sensitive elements of the change. If this is not done, the “survivors” are often left feeling ignored and disrespected as they consider just how they company will treat them going forward. The survivor syndrome is a key element that is too often mismanaged.



I think those categories might be helpful at a high level. Gantthead also has a number of articles on knowledge transfer that might be helpful as well.

avatar
Dirk Kittredge Project Manager| Marex Group Centennial, Co, United States
Why would this be any different than any other project? If I were approaching this problem, I'd consider each person individually with related task sets. If some have special needs, I'd consider them individually, else group them into like situations (managment people may have different requirements than programmers, etc.). You can then determine the necessary timelines for each with appropriate lead times, related tasks, etc. Just my opinion...
avatar
Dave Garrett
PMI Team Member
Senior Advisor to the CEO| PMI Sterling, Va, United States
Dirk is right. Certainly each project and person is different. So we shouldnt lump them all together. However, if you look at the list I posted below and see how it applies to each situation - I think it might be helpful.
avatar
Doug Nixon Sth Yarra, Vic, Australia
I think Dave's checklist approach is a great start. It's important to take a holistic approach at the planning stage. It's then easier to deal with individual as you go through the execution. You will need to understand the logical (task driven) and the emotional perspectives. The emotional dimension will affect each person individually and they will need to be dealt with as such.

Please login or join to reply

Content ID:
ADVERTISEMENTS

"If at first you don't succeed, try, try again. Then quit. There's no use being a damned fool about it."

- W. C. Fields

ADVERTISEMENT

Sponsors