CMM - Introduction

This blog is intended to develop an understanding of CMMI so that process improvements can be better applied by its reader to their projects.

• What is CMM?
• Why CMM?
• What are it's characteristics?
• What are CMM levels?
• What are Key process areas?
• What should a project do to be at Level 5?
• What are the benefits?

These are some of the things we will look at in this blog various posts. This is the first in the series of posts that will explore CMM.

WHAT?

There are lot's of definitions for CMM. One good one is this:

It defines how software organizations mature or improve in their ability to develop software

The model was developed at Software Engineering Institute of Carnegie Mellon University in late 80s.This model provides a structured view in a five-layer model of increasingly sophisticated practices for those working in software. Each level (except Level 1) has certain Key Process Areas associated with it. Each level addresses levels of maturity exhibited by the project.

CMM assessment (Note: It is not called certification) is a detailed procedure. There are no certificates awarded after the assessment. Trained internal assessors+External assessors do the assessment. Other than this, organization should have project level CMM assessment which should be done every month. These are done by SQAs and other trained assessors.

WHY?

CMM describes how software organizations can take the path of continuous improvement which is so required in this highly competitive world. Moreover, it is a model that can be tailored to suit your organization. Keep Improving - is the CMM mantra. CMM creates lot of brand value and also many organizations are demanding it.

In this blog, CMM - Capability Maturity Model for Software is being discussed.

Next - CMM Overview

Read more...