The software process movement is described. Organization-wide software processes and the maintenance of defined software processes are considered. It is suggested that the software process movement will find the software maintenance community directly in its mainstream. Even more important, the maintenance community is about to face a double challenge. First, it must struggle to adopt more effective processes, and the Capability Maturity Model offers some guidance in doing so. Second, the software maintenance community must bring its considerable skills and experience to the process community's aid in determining how best to maintain the processes defined for software organizations. >