Thursday, November 1, 2007

How do we avoid bulky processes when using the CMMI?

We are in the process of defining our process artifacts after a CMMI Gap Analysis . Due the lack of experience in CMMI I am finding the definitions we are creating are too bulky and that worries me lot when I think of the implementations . Suppose we define all that is required , how can we best take extracts and publish it in a QMS system for others to practice?

Remember this:


Sometimes, "lack of experience" is exactly the RIGHT thing needed to be successful! I like the way you're thinking - don't stop doing that!

Usable and useful processes are a pre-requisite for any company to be successful, and too many go down the road of "over-interpreting" the CMMI so that you end up with heavy, burdensome processes that are not useful. Remember, your engineers are not there to "follow the CMMI," they are there to build creative solutions to business problems using technology.

One common mistake is trying to implement a process that includes all of the "typical work products" and "subpractices" within each specific practice. This was never the intention of the model. These are only examples, and are not "required" components of the CMMI.

What you need to do is internalize the meaning of the practices and goals in each process area and piece together a puzzle that shares work products and procedures across many process areas - in other words INTEGRATE don't REPLICATE.

Once you've identified all of the processes and work products conduct a CONSOLIDATE exercise where you consider the data in each work product and determine ways to reduce and eliminate documents by combing similar data, the ELIMINATE redundant and useless data.


No comments: