Proper interpretation and understanding of a model is a vital part in any new model implementation in an organisation. During the course of action, we have a tendency to over simplify things and thus ignore certain key aspects. And in certain cases there happen some misconceptions too. This article tries to clarify such ignored aspects and the next article will talk more on misconceptions in CMMI implementation. There might be some overlapping between these two articles.

The below aspects are easily skipped, not because they are too tough to implement but because, they are too simple to implement.

  • GPs – Ignored
    • The Generic Practices (GP’s) represent the most important part of the model. Poor implementation of GPs will always lead to process failure. Usually we will try to map all specific Practices (SPs) of each PA and simply ignore GPs. In some cases GPs will be mapped automatically through SP implementation itself, but not in all cases. GPs are the most beautiful aspect of the CMMI model as it talks about institutionalising the process
  • CM – Oversimplification

Some natural synergies exist between the generic practices and their related process areas as explained in Evidences supporting implementation of CMMI GPs.

Here the ‘recursive relationships between generic practices and their closely related process areas’ are explained.CMMI GPs-PA

For more information on required evidences for each generic practices, please refer Evidences supporting Implementation of CMMI GPs

Many process areas address institutionalization by supporting the implementation of the generic practices. An example is the Project Planning process area and GP 2.2. To implement this generic practice we need to implement the Project Planning process area, all or in part. In the below table such related process areas ( which are supporting the GPs) as well as required artefacts( which could be the evidences for the implementation of GPs) are shown.

In addition to this normal GP-PA relationship, there are some recursive relationships between generic practices and their closely related process areas. This is explained in How does the Generic Practice recursively rpply to its related Process Area(s)?