Skip to content

CMM (Capability Maturity Management)

August 3, 2009

CMM (Capability Maturity Management)
CMM is process capability model based on Software development organization Practice. CMM was developed by SEI (Software Engineering Institute) at Carnegie Mellon University. It was initially founded by Military Research.

Structure of CMM
CMM involves the following aspects,
1. Maturity level
2. Key Process Areas
3. Goals
4. Common Features
5. Key Practices
We will see these aspects briefly,
1. Maturity level
Maturity level is the layered framework. This is engaging thru the continuous improvement. It is important to state here that an organization develops the ability to assess the impact of a new practice, technology, or tool on their activity. Determine how the innovative efforts influence in existing practice. This empowers the projects, teams and organizations.
2. Key Process Areas
KPA is a cluster of related activities. Performed collectively and achieve a set of goals.
3. Goals
The goals signify the scope, boundaries, and intent of each key process area.
4. Common Features
Common feature includes the practice of the standards. There are five common features available they are,
Commitment to perform
Ability to perform
Activities performed
Measurement and analysis
Verifying Implementation
5. Key Practices
Key practice is describes the elements of infrastructures and Practices.
There are five levels of CMM according to SEI,
Level1- Initial
Level2- Repeatable
Level3- Defined
Level4- Managed
Level5- Optimized
Let???s have look these levels briefly,
1. Level1- Initial
The starting point for use of new process
Process are not defined, the changes are based on the user or event. The organization does not have the stable environment. Level 1 company frequently exceeds the budget and schedule for the project. Due to lack of formality the level 1 organization facing some problems like over commit and abandon process
and unable to repeat the past success. Level 1 organization is often seen as a service instead of partner.
2. Level2- Repeatable
Process is used repeatedly
Some software development processes are repeatable, possible with a consistent result. The process may not be repeated all the projects in the organization. These organizations will use some basic project management to track cost and schedule.
3. Level3- Defined
Process is defined and confirmed as a standard process
These organizations have defined some set of process and follow the defined standards. Projects establish their defined processes by applying the organizations set of standard processes.
The critical difference between Level2 and 3 is scope of standard, Process descriptions and procedures. At level 2 these may be quite different in each particular project, but in Level 3 these are set as organization standards and it will maintain as stable.

4. Level4- Managed
Process management and measurement takes place
Using process metrics, management can effectively control the process for software development. Management can identify the ways to adjust and adopt the process to particular process without loss of quality.
These organizations set the quality goals for software process and maintenance. Critical difference between Level3 and 4 is predictability of process performance. In Level4 the performance of the process is controlled using statistical and other quantitative techniques.

5. Level5- Optimizing (process improvement)
Process management includes deliberate process improvement.
Level 5 organizations focus on the continuous improvement of the process performance both incremental and innovative technological improvement. The Quantitative process improvement of the organizations is established, continually revised to reflect changing business objectives, and used as criteria in managing process improvement.
1. Creation of Software specifications, it contains what is going to develop and formal signoff and approval mechanism.
2. Technical specification contains how the things specified in the Software specifications are going to develop will be used. This is living document.
3. Peer review of code: Allow developer to walk through an implementation and to suggest improvements or changes.
4. Version control: Large number of organizations has no formal revision control mechanism in place.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: