Software handover is a de facto process in all software organizations. It is one of the most business critical and complex processes. It is also one of the most diverse processes, and thereby, one of the most difficult processes to define. Despite this, software handover is not well recognized within the academia. Right now, there are no software handover process models whatsoever although software organizations desperately need guidelines for how to perform this important and critical task. To aid them in defining their handover process models, we are in the process of creating Evolution and Maintenance Management Model (EM 3 ): Software Handover focusing on handover (alias transition) of a software system from developer to maintainer. In this paper, we evaluate one of the EM 3 components, Management and Administration (MA), addressing activities for planning and controlling the transition process, its schedule, budget and resources. We do it within 29 organizations. Our primary goal is to find out whether the component is realistic and whether it meets the needs and requirements of the software industry today. Using the feedback from the industry, we tackle process diversity using the C ontext- D riven P rocess Orchestration M ethod (CoDPOM). / <p>QC 20120223</p>