4.5 Example of “Potential Weakness” Against CMMI in
an Agile Organization
Somewhere during every interview as we are talking about how the individual
executes his or her job, we get to the products they produce as part of
executing that job. Eventually, I ask:
Who else looks at these products you are producing?
This discussion leads to the question about whether they conduct peer
reviews on their products. Often the answer I get in Agile organizations is:
We don’t do formal peer reviews on our products.
On the surface, this triggers a “potential weakness” against the CMMI model
because peer reviews are a specific practice in the Verification Process Area of
the CMMI model. We don’t have enough time to dig into each area I identify
as a potential weakness during the one-hour interview. In most areas where I
find potential weaknesses, I just make a note that those areas require more
investigation and probably further discussion.
As an alternative, I could just list as part of my report all the areas my client
must fix to “comply” with the CMMI model. I could tell them I heard you
don’t do peer reviews and you need to do peer reviews because it is an
expected practice within the CMMI. This is actually how I have observed the
CMMI model used in many organizations. It is an example of using the model