This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Due to a family problem I have decided to relocate to NCR Delhi. I do not want to switch the company as I believe in working with the company for longer time. I need advice from other members on what should be the correct way to make this relocation possible. There are few ways in my mind to try this but I am not sure which would the fruitful way. One way I can think of is sending email to RMG (Resourcing manager) of current location and tell him trough email followed by phone call. Another way is to talk to current manager and tell him the problem. Another way I can think off is contacting project managers and HRs in Delhi NCR (desired location) and telling them the problem. I am not sure whether any of these ways would work. I need advice from others in forum on what approach they think might work.
After reading the handbook (if it exists), talk to your current manager. He might have undocumented advice. And even if not, he should know. Unless your company has specific rules on transfers, whomever else you ask will ask your current manager how you are as a worker. You don't want him to hear this from someone else.
You need to keep in mind that relocation might not be just defined by the support your manager provides. Budgeting will be definitely a major factor. I know some companies who prefer certain teams operating out of specific locations e.g. Backend dev from location A, QA from location B etc. These kind of policies usually help the company in the management functions. One more influencing factor could be the client preference, if you are working on an outsourced project. Thus my original suggestion to refer to the employee handbook