First, the idea itself of putting a time frame for CMMI ML3 in one year or nine months or 'n' months is not a good way to start the CMMI journey.
Before estimating the number of calendar months, a CMMI Gap Analysis should be performed. How can anyone estimate the time frame for CMMI Implementation before one knows the implementation scope? Gap analysis is a definitive way to establish the scope. However, it must be remembered that a detailed gap analysis in terms of SCAMPI C or SCAMPI B should be performed later on in a CMMI Program to establish all the low-level gaps.
The other aspect related to time frame is about the rigour of implementation which depends on two factors. First is the intent to implement CMMI practices in an appropriate and adequate manner. And it takes time to understand and implement each of the CMMI practice in the "right way". And second is the time frame allowed for practices to reach the state of full deployment followed by them getting stabilized and finally matured. Only after that an organization should consider external validation of their internal CMMI maturity. In the post SCAMPI v1.2, it is highly risky for an under-prepared or ill-prepared organization to even attempt an external CMMI ML3 appraisal.
Top executives and senior managers often rush into CMMI ML3 and at times without adequate resources (in terms of staff, tools and infrastructure). This is a common occurrence in organizations that have already other certifications like ISO 9001 or internal audits or assessments against internal process system. This approach will, in no case, yield in true benefits from CMMI accruing to the organization. And not just that, even the management dream of seeing the statement "We are a CMMI ML3 Organization" in the Proposal Template may remain unfulfilled, if the external CMMI Appraisal (SCAMPI A) fails.
No comments:
Post a Comment