CMMI generally has a pretty poor reputation amongst… well everyone except the process geeks. It is generally perceived as bureaucratic, pedantic, heavyweight and ultimately ineffective.
So you can imagine my joy when my boss recently said we have been given a target of achieving Level 2 by the end of the year and Level 3 by the end of 2012.
My first reaction was to find out more about CMMI; it’s purpose, structure, goals and practices. A quick look at the SEI website and the v1.3 model for development revealed some interesting facts:
CMMI is method-agnostic; it doesn’t matter whether you use PMI, PRINCE2, Scrum or DSDM Atern, the goals are the same.
The goals are actually things you should be doing anyway. Things like planning, requirements management, engaging stakeholders, project monitoring and so forth.
CMMI provides a list of practices for each process area, but does not tell you how to implement those practices.
I am now, much to my own surprise, confident that, not only can we achieve Level 2 this year, we SHOULD. After all, achieving Level2 is not the real objective. But CMMI can provide us with a model for complying with Atern’s eighth principle – Demonstrate Control.
We have a consultant visiting us on Friday to see the way we work. It will be interesting.