CMM-Based Appraisal for Internal Process Improvement (CBA IPI): Method Description

This document is a high-level overview of the CMM SM -Based Appraisal for Internal Process Improvement (CBA IPI) V1.1 assessment method. It provides a brief history of SEI appraisal methods, as well as establishing appraisals in the context of the IDEAL SM approach to software process improvement. CBA IPI is a diagnostic tool that supports, enables, and encourages an organization’s commitment to process improvement. The method helps an organization gain insight into its software development capability by identifying strengths and weaknesses of its current processes related to the Capability Maturity Model SM for Software V1.1. The method focuses on identifying software improvements that are most beneficial, given an organization’s business goals and current maturity level. Brief descriptions of the method activities, roles, and responsibilities are provided. In addition, guidelines are provided for establishing resource requirements for conducting a CBA IPI. The SEI Appraiser Program is discussed, detailing the requirements for persons qualified to lead CBA IPIs. 1 Why Was CBA IPI Created? Using the Capability Maturity Model SM for Software V.1.1 (CMM) as a reference model [Paulk 93a, Paulk 93b], the Software Engineering Institute (SEI) developed the CBA IPI V1.0 in 1995 for assessing an organization’s software process capability. CBA IPI V1.1 was released in 1996 containing modifications for clarification and simplification. In-depth documentation and guidance on the CBA IPI method [Dunaway 96] is available through CBA Lead Assessor Training. 1.1 History of SEI Appraisal Methods In accordance with the SEI’s mission to provide leadership in advancing the state of the practice of software engineering by improving the quality of systems that depend on software, there has been strong emphasis within the SEI on treating software development tasks as processes that can be defined, practiced, measured, and improved. In early software process publications, a software maturity framework [Humphrey 87a] and questionnaire [Humphrey 87b] were developed to help organizations characterize the current state of their software practices, set goals for process improvement, and set priorities. Software process is defined to mean the system of all tasks and the supporting tools, standards, methods, and practices involved in the production and evolution of a software product throughout the software life cycle. It has become widely accepted that the quality of a