Doing CMMI the Lean Way

CMMI is an excellent framework for the management, execution and improvement of business processes. Talking more specifically about CMMI for Development (CMMI-DEV), adoption of the practices enumerated as part of the various Process Areas of this CMMI framework is a definite way to attain an efficient and effective way of working.

There is however a perception amongst many that CMMI calls for a lot of documentation. This perception is entirely incorrect as people fail to understand the crucial difference between thinking, doing and documenting and at the same time also fail to understand the linkage between doing and documenting. Suppose one takes the example of the design of a component. The designer will conjure various alternative design concepts in his mind, evaluate them and then select the optimal design concept. The selected design concept becomes the basis for subsequent implementation but this is possible only when the design is specified in black and white, in a structured manner (using a standardized design specification template is the way to go - there may be more than one standard template to take care of the design for a big, complicated product versus a small, simple product).

What did the designer 'do'? Design obviously, but how can anyone confirm the effectiveness of the design? That's where 'do-cumenting' helps. In a commercial context checks and balances are important to ensure cost-effective, on time, good quality delivery in a consistent and profitable manner. Documenting also ensures that the person doing the activity commits to the work performed.

So it is clear that documentation cannot be wished away. Can it be reduced or rather optimized? Yes, and that's what can help in doing CMMI the lean way. Lean CMMI doesn't mean doing less than required but doing what is just enough. Lean implementation is based on the premise of waste reduction. All steps in the process that can be removed should be removed. However, effectiveness of doing shouldn't get impacted in the name of reduced documentation.

Lean CMMI would in fact mean do as less as possible but document all that has been done. It doesn't mean doing more and documenting as less as possible.