A software process definition embodies a complex interaction of development and management activities, products, tools, and metrics. Establishing an initial process definition for any organization is a difficult and time-consuming effort. Modifying the initial definition also represents an intense effort that requires a well defined process of organizational coordination and communication. Organizations could reduce much of the cost associated with the modification of a software process if the initial definition included a viable planning method for tailoring a generic process to each project rather than forcing the project to fit a standard process. This paper is based on a planning method that has evolved within TASC, it describes the steps required to create a tailored process definition for specific projects based on the generic process definition.