Updated revision of the best selling book on CMMI - now covering version 1.2.

Sandy Shrum is the CMMI communications coordinator and is a CMMI author, reviewer, editor, and member of the Quality Assurance Team Mary Beth Chrissis is a member of the CMMI Architecture Team and is the CMMI training manager Mike Konrad is the leader of the CMMI Model Team and chair of the CMMI Configuration Control Board

Capability Maturity Model Integration (CMMI) is a process improvement maturity model for the development of products and services. It consists of best practices that address development and maintenance activities that cover the product lifecycle from conception through delivery and maintenance. This latest iteration of the model as represented herein integrates bodies of knowledge that are essential for development and maintenance, but that have been addressed separately in the past, such as software engineering, systems engineering, hardware and design engineering, the engineering "-ilities," and acquisition. The prior designations of CMMI for systems engineering and software engineering (CMMI-SE/SW) are superseded by the title "CMMI for Development" to truly reflect the comprehensive integration of these bodies of knowledge, and the application of the model within the organization. CMMI for Development (CMMI-DEV) provides a comprehensive integrated solution for development and maintenance activities applied to products and services. CMMI for Development, v1.2 is a continuation and update of CMMI v1.1 and has been facilitated by the concept of CMMI "constellations" wherein a set of core components can be augmented by additional material to provide application-specific models with highly common content. CMMI-DEV is the first of such constellations and represents the development area of interest. Purpose The purpose of CMMI for Development is to help organizations improve their development and maintenance processes for both products and services. This book is based on CMMI for Development, v1.2, which was produced from the CMMI Framework 1 in August 2006. The CMMI Framework supports the CMMI Product Suite by allowing multiple models, training courses, and appraisal methods to be generated that support specific areas of interest. A constellation is a collection of CMMI components that includes a model, its training materials, and appraisal-related documents for an area of interest. Currently there are three planned constellations supported by the v1.2 model framework: development, services, and acquisition. "Additions" are used to expand constellations for specific additional content. This book contains the CMMI for Development constellation and contains both the base CMMI-DEV as well as CMMI-DEV with the IPPD group of additions (CMMI-DEV +IPPD). If you are not using IPPD, ignore the information that is marked "IPPD Addition" and you will be using theCMMI for Developmentmodel. CMMI v1.2 Contributors Many talented people were involved in the development of the CMMI v1.2 Product Suite. Three primary groups involved in this development were the Steering Group, Product Team, and Configuration Control Board. The Steering Group guides and approves the plans of the Product Team, provides consultation on significant CMMI project issues, and ensures involvement from a variety of interested communities. The Product Team writes, reviews, revises, discusses, and agrees on the structure and technical content of the CMMI Product Suite, including the framework, models, training, and appraisal materials. Development activities are based on multiple inputs. These inputs include an A-Specification and guidance specific to each release provided by the Steering Group, source models, change requests received from the user community, and input received from pilots and other stakeholders. The Configuration Control Board is the official mechanism for controlling changes to the CMMI models andIntroduction to CMMItraining. As such, this group ensures integrity over the life of the product suite by reviewing all proposed changes to the baseline and approving only those changes that satisfy the identified issues and meet the criteria for the upcomin