Why was the CMMI Project initiated?
The CMMI Project was initiated based on a 1997 review of Software Engineering Institute (SEI) activities by the Office of the Under Secretary of Defense (OUSD) and interest expressed to the SEI by the CMM user community.
What were the requirements for CMMI?
Requirements are published in a specification developed by the CMMI Steering Group entitled A Specification for the CMMI Product Suite (A-Spec).
How was the scope of the CMMI project determined?
The CMMI project was formed to improve the usability of CMM technology for a set of disciplines including and extending beyond software engineering. As the CMMI concept developed, the scope of the project was restricted to a few disciplines most needed by government and industry until the concept was proven.
The selection of software engineering, systems engineering, and integrated product development CMMs was made by industry and government participants for the initial proof-of-concept phase. However, the product suite was designed to accommodate expansion of its discipline coverage and product and project lifecycle coverage.
Which models were used to build the initial CMMI models?
The following models were used as sources in the development of the first set of CMMI models:
SW-CMM Version 2 Draft C
EIA/IS 731 (SECM)
IPD-CMM Version 0.98
Who was involved in developing CMMI?
Members of industry, government, and the SEI were involved. The project was sponsored by the Office of the Secretary of Defense (OSD) and the National Defense Industrial Association (NDIA) Systems Engineering Committee.
Project members belonged to one or more groups, including the Steering Group, product team, stakeholders/reviewers, configuration control board, and CMMI steward.
What are the roles of the CMMI product teams?
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 and Introduction to CMMI training. 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 upcoming release.
The CMMI steward (i.e., the SEI) ensures the quality and widespread availability of the CMMI Product Suite, supports its adoption, and facilitates its maintenance and evolution.
How do commercial organizations participate?
Commercial industry product developers who use CMMs have participated as members of the product team, the CCB, and the Steering Group.
How do the Military Services participate?
Each Service provides members to participate on the CMMI Steering Group, the product team, and the CMMI CCB. |
