Software process improvement often lacks strong links to project management and control activities, which are concerned with identifying the need of process change and triggering improvement initiatives. Project management, on the other hand, often fails at selecting appropriate software engineering methods and technology that help to ensure project success. This paper proposes a model that guides project managers (1) to set up a project so that it can reach its specific goals and (2) to identify corrective actions (or changes) once a project is at risk of failing its goals. The model complements established improvement methods such as CMMI, GQM, and Experience Factory and links them to those project management activities that often are the starting point of improvement initiatives.