It’s not easy for a PM to adopt himself into a domain where he has no connections. PM can be thrown out of his field to work for another but before working under a project which is not related to him, he should learn basic ideas of the project and its process.
Lets’s take two different PMs working in a Constructions projects and Software Developments.
PM who does works in construction of buildings has huge vision of the plan, field work, requirements of a construction depending upon its use, maintaining the quality and problems that should be faced in each and every step. Only he can estimate the time period required to complete a manual work.
PM who does works in Software developments has immense knowledge in scheme and strategy for a particular software project. He would have huge plan regarding the design requirements, programming platform, testing of the software and difficulties he would face if the project gets to some complications.
When this both PMs are expert in their own field, its not easy for them to change their positions since they don’t have any proper idea for other field. Since PMs major work is to interact with people’s minds, team members would be reluctant to take the word of PMs who is from other domain.
Its better to be where they are. But in case if there comes a situation where one must take up the work in other domain, he should learn details from the prior projects done by the domain.

Akshaya Kirithy Baskar