This method therefore requires constant communication with the workers to ensure they understand how the process was developed. PATs focus on one process area or one thread of software engineering that covers multiple process areas, whereas the Ivory Tower approach addresses the entire process improvement effort. They define the process based on current practices, then create additional processes that fill specific CMM key process area requirements. This is the most common approach to define processes, and is usually used to implement improvements incrementally in organizations that view process improvement as a long-term investment. It requires the SEPG to handle the institutionalization aspects and track the interfaces between process areas.
Nothing breeds success like success.
The key to making this method work is to define the environment in which the process was successful. This method works well in organizations that are resistant to process improvement, i.e., project teams that will likely fight processes that have not been used in practice. The knowledge that successful projects have used the process makes buy-in more likely. However, these processes may be incomplete according to the CMM and may need adjustment in the future. Unfortunately, this method focuses on creating documented processes, complete or not.