like the idea behind it, but may not completely buy into the idea without a little more explanation. Therefore, it's important to present CMMI to the company in a simple and straightforward manner. One good way to do that is to make a PowerPoint presentation that explains what CMMI is, its purpose, how it works, and the benefits of implementing it.
It's also important for the presenter to discuss the four main process area categories and the 22 process areas that make up CMMI. Using actual data measuring success rates of other companies who used CMMI is also a good thing to add in the presentation. The company needs to understand that their expense in implementing CMMI is actually an investment, and
19
the ROI is much more profitable for the company in the long run.
This is perhaps the most important aspect.
A company is a business, and business is always centered on making good investments. CMMI should be presented as an investment that will pay off consistently and continuously.
20
The Evolution of the CMM
In the late 80s, the American Software Engineering Institute (SEI) in cooperation with Mitre Corporation developed an architectural model that will aid the US federal government on evaluating objectively software providers proposals in managing the US government large projects. This architectural model is known as the Capability Maturity Model (CMM).
CMM is a model that represents the process maturity for software development. The advanced model shows the progress of a companyOs abilities to develop software. When companies seek the services of software developers it is necessary that they know as to when the deliverables can be served. Yet many companies complete their projects, it showed that there were significant overruns in terms of schedule and budget. With the CMM, such problems were solved.
The main concept of the CMM standard is the organizational maturity. A company is considered as a mature organization if it has clearly defined procedures as to how their software is developed and procedures in terms of project management. As software companies expand, these procedures need to be adjusted and perfected as needed.
CMM is the standard followed by software development
company in the process of development, testing, and software application; and rules for appearance of final program code, components, interfaces, etc.
The evolution of the CMM made a major milestone in the management of software process. It was at that point where the software community had a full descriptive understanding how software companies "mature" or improve, in their ability to develop software.
21
To Be on CMM Level 5
The Capability Maturity Model (CMM) is a standard guide for software developers in the development and refinement of an organization's processes. The CMM has 5 levels of maturity.
These are Level 1 (Initial), Level 2 (Repeatable), Level 3 (Defined), Level 4 (Managed) and Level 5 (Optimizing). A mature
organization depends on its capability of providing the software development at a specified time. The CMM can be considered as a benchmark used for assessing different organizations for equivalent comparison.
If your organization falls under the CMM level 5, you have achieved the highest level of maturity and your organization focus is on continuous process improvement based on quantitative feedback and pilot of new ideas and technologies. There are software project teams created by organizations to analyze the defects and determine their causes. The team evaluates to prevent the recurrence of known defects and the lessons acquired are shared to other projects. At CMM level 5, the word waste is unacceptable. Teams should organized efforts in removing the waste, without necessarily changing the entire system.
Improvement is brought about by any incremental advancement in the existing process and by innovations with new
technologies and methods. Technology and process improvements should be planned and managed as regular business
activities. CMM level 5 are audited and reviewed. A result of the rating is published by the software organization. Most organization uses this result for marketing purpose of drawing more customers and for customers to rely on their software.
Aim high, aim for CMM level 5. It may be your ticket entry into the global software development-sourcing arena.
22
Calibrating the CMM
Capability Maturity Model (CMM) is the standard process improvement for software developers. Software organizations to be able to move towards next level is to see to it that the levels defined on each maturity level are met. Process improvement is a continuing process and promotes higher quality of product.
One way to find out on how to further improve your work process is through calibration.
Calibration is the act of comparing two instruments or measuring devices, where in one is standard of known accuracy that can be traced to a national standards. CMM calibration aims to detect, correlate, report, or eliminate through adjustment a work process that results to discrepancy in accuracy being compared with the standard.
The measurement of uncertainty is part of the CMM calibration process. It is necessary that calibration and measurements used are traceable in order to be accepted by outside
organizations. This is commonly accomplished by making a comparison with the standard. In short, calibration is comparing representative of projects performing under the same life cycle strategy and within the common business domain. Calibrations can also involve modeling the effort distribution and schedule results into the phase of governing life cycle model.
The CMM calibration will help software organizations in improving the system being modeled. The process currently practiced can be adjusted if need be. Organization can plan for future implementation based on the calibration activities carried out, applying new tools and technologies and the choice of alternative process.
Start calibrating your work process, and check if they are within the standard or higher.
23
The Old CMM and the New CMMI
The Capability Maturity Model (CMM) also known as
CMM for Software (SW-CMM) was created by Software Engineering Institute (SEI) in 1986 to aid the Department of Defense in assessing the software contractor bidderOs ability in the delivery of government contracted software project. In December 2007, the SEI renamed the CMM to Software Engineering CMM
(SE-CMM). The CMM has been retired and was replaced by Capability Maturity Model Integration (CMMI).
Capability Maturity Model Integration (CMMI) was developed and introduced as an answer to the confusion of software developer in the use of multiple improvement maturity
models. CMMI is a process improvement approach that gives organizations with the essential elements of effective processes.
It is used as a guide in the process improvement of a project, a division, or an entire organization. CMMI helps in the integration of the traditionally separate organizational functions. It helps in the setting up of process improvement goals and priorities and provides guidance in quality processes. It also provides the reference point in the appraisal of current processes. CMMI provides the process requirements for organizations to conform in the development and maintenance of systems and software products and services. The CMMI was said to be the successor of the three source models namely:
1. The Capability Maturity Model for Software (SWCMM)
v2.0 draft C
2. The Systems Engineering Capability Model (SECM)
3. The Integrated Product Development Capability
Maturity Model (IPD-CMM)
24
The CMMI provides the best practices