Today?s context of software development requires a certain amount organization to build products and Process Definitions appear as an attempt to formalize and structure the set of steps, followed by a team, with the objective to deliver a final product with quality. Within this context, Software Reuse emerges to increase the company?s profit and make possible the reuse of components produced in previous projects. The benefits provided by the introduction of reuse discipline is to increase a team?s productivity and the proper development of reuse based products also requires a determined activities guide, also contemplated by a Reuse Process definition to help teams realize the development. Nevertheless, the introduction of reuse processes, into organizations that already have established functional practices, is even a more complex activity because it is important to preserve the institutionalized habits and not to drastically change the practices properly executed by the team. In this scenario, an Adaptation, to introduce reuse driven development process in an organization that already has a non-reuse development process, is necessary so that to minimize barriers of a new process deployment. Therefore, this work has the objective to present an Adaptation Process that links characteristics from a reuse and non-reuse development process in order to generate a common description that collects characteristics and specification from both process scenario