03 July 2006

Sample from the CMMI FAQ... and it's working title.

Well, after putting fingers to keys to answer some of the CMMI FAQs, I've been able to conjur-up a name:

Entinex' brutally honest, totally hip CMMI FAQ.

Here's a sample question (and answer):

Q: How long does it take?

A: Here's another one of those dead give-away questions that a company is more interested in the rating than the improvement.

OK, that's a little unfair.  Let's just say that as often as we hear this question, our judgmental attitude holds for ALMOST everyone who asks it.  Alright, so maybe you are the exception.  The truth is, it's a fair question.  For every company. 

A rare few companies don't care how long it takes.  Lucky them.  Applying a generous dose of benefit of the doubt, we can assume that the question is asked not for "how soon can we get this out of the way?" as much as from "are there any rules that dictate a minimum time before performing an appraisal?" How we can tell whether the company is interested in the improvements vs. the rating is simply a linear function of how long into the conversation we are before it gets asked. All-too-often, the source of the question is less ignorance of the process and more ignorance of the point behind going through the process.

Process improvement purists wish more people were more interested in the journey than in the destination.  We are process improvement pragmatists.  We know you're not looking at CMMI because you had nothing better to do with your time and money.  That's for Bill Gates and his very worthy charitable endeavors.  The company he's famous for founding is still in business for the money.  FAST.  So, how long it takes is a real question regardless of how you spend your money.

Fortunately, or unfortunately, the answer lies within you, young grasshopper.  Really.  We can't give you a much better answer than that.  What we can do, however, is give you a list of the attributes that you can use to estimate how long it will take you, and give you a few example cases and some very general time-ranges.

Let's start again with our favorite analogy.  Say you're carrying around about 40lbs (18.18kg) of excess body fat.  How long will it take you to lose the fat?  A year?  Two?  6 months?  Can one person do in 6 months what another person needs 2 years?  We all know the answer to these questions.  "IT DEPENDS!"

EXACTLY!  How quickly a company can become rated to a pre-determined point in the CMMI's rating scale depends entirely on them and their circumstances.  It depends on:

  • their level of commitment,

  • their tolerance for and ability to implement change,

  • how busy they are,

  • what they know about process improvement in general and CMMI in particular, and

  • it depends on where they are as a starting point and

  • how much of the organization they want to include in the rating.

Working backwards from the appraisal itself, the absolute minimum calendar time a company should expect between when the starting gun is fired and when they cross the finish line is a simple matter of logistics.  Probably about a month if they're lucky.  Two months would be more realistic.  These 2 months, of course, are just the logistics and prep-work necessary to plan and conduct the appraisal and the activities that lead to an appraisal.  Obviously, this time frame would only be realistic if the company was completely ready for the appraisal, had done all their homework, knew exactly what the state of their process implementation was and were literally trying to do nothing more than figure out how much time they had before they could conduct the appraisal.  Of course, such a company wouldn't be asking the question.  They'd already know.

So then there's almost everyone else. Everyone else needs time to first determine where they are in their implementation of CMMI practices.  This is like saying, first we need to find out how much excess fat we're carrying around.  A trip to the right physician would answer this.  For CMMI, it's called a "Gap Analysis" and can take a week or two.  Then, depending on those factors bulletted earlier, the gap found by the analysis would need to be filled.  This is the part where a company would need to figure out what it's optimum sustainable diet and exercise routine should be, and, how long to stick with it to see the desired results. 

In CMMI v1.1, there are 25 Process Areas.  The duration of the gap closure activities would also be a function of how many (and which ones) of the Process Areas the organization wanted appraised.  Each of the Process Areas could be analogous to some aspect of a healthy lifestyle such as food choices, food quantity, shopping, cooking, meal planning, exercises, frequency, repetitions, technique, equipment, blood work, rest, stress management, work environment, time management, and so on.  Obviously, the more of the lifestyle someone wanted to adopt, the longer it would likely take.

Once a gap is filled (i.e., the weight is lost), an organization should give itself at least 3 months on the short-project end to 12 months on the larger project end to actually use their processes.  This would provide them with enough data to actually conduct an appraisal.  On the fat-loss analogy, this would be like finding that point where diet and exercise are enough to keep the weight off and one is able to demonstrate to themselves (or others, as needed) that they can, in fact, live and sustain a healthy lifestyle -- in the face of temptation and other uncertainties.

Once people internalize how process improvement works, how long it takes to earn a rating is a question such people stop asking.  Like fat loss, process improvement is a discipline backed by many best practices.  And, just like weight loss, people are still seeking a "silver bullet".

We, on the other hand, stick to a healthy diet and exercise program.  When we're off track we know it.  We gain fat and feel like crap.  When we're on it, we see the results.

Make sense?

3 Comments:

At 07 July, 2006 15:16 , Anonymous Karyl Owings said...

Yes, this makes sense - it's a good way to explain timing to those who don't know CMMI in detail, yet expect those of us who do have the details to implement solutions. I've a question, though, about your citing of 3 to 12 months of process operation to generate enough data for an appraisal. Could you discuss your rational for choosing those numbers, and why such a wide range? If we're waiting that long for an appraisal, then we're also waiting that long for numbers that tell us whether or not our processes are operating according to expectations (or hopes). In today's environment, can businesses afford to wait that long for numbers that enable better decision-making? They'll all say they can't...thereby providing us with another point in favor of undertaking use of the CMMI model more for process improvement than to get that rating: Producing useful numbers quickly allows management to make better decisions sooner. Therefore, it behooves us to design measures that will produce useful results quickly - but then, if the business is using those numbers to manage process & product....why wouldn't they be ready for appraisal? Why undergo a 3 to 12 month wait - wouldn't the true answer be, "You're ready for appraisal when you're using your metrics results to make business decisions"? Do not pass Go, do not collect $200, head straight for Level 4.

 
At 08 July, 2006 23:27 , Blogger Hillel said...

Thanks for the question, Karyl.
Your input is long so for skimmers I'll pull your question out here so they don't have to go digging for the specific thing I'm answering.

You asked:

"... about your citing of 3 to 12 months of process operation to generate enough data for an appraisal. Could you discuss your rational for choosing those numbers, and why such a wide range?"

The reason for the range has to do with the types of projects an organization is working on, as well as the way in which they're implementing the processes.

Some practices don't get invoked as often as others, and, depending on the Process Area, they might need to wait a number of cycles before they can determine whether the process works.

Because of this, an organization would certainly want to wait a bit before being appraised or they might not have practices doing what they're supposed to be doing and going into the appraisal saying stuff like, "... we know this evidence shows that we're not doing a practice, but our QA practices caught it and we're working to fix it."

Well, hurray for QA! But, that doesn't do for the practice that's not being done, right?

Certain projects can offer the organization the opportunity to use all its practices in a short period of time, but others take longer. It could be easy to over-generalize this by saying smaller projects vs. larger projects, but that's not always true. That's why my answer said the 'types' of projects. Some large projects move quickly and some small projects move slowly... Some projects are large on paper because of the money involved, but in effect are not so complex, other projects might not add up to many person-hours but every minute and every decision is critical.

Not knowing anything about a given reader's projects, this range is often wide enough to account for enough time for even practice implementations that take place annually to be accounted-for when preparing the evidence needed for an appraisal.

I agree with your assertion later in your comment about the need for processes to produce decision-supporting data. Processes are fairly worthless if they don't support business needs at the executive level and at that level what they need is business intelligence. At the risk of being self-aggrandizing, I have a detailed presentation (here) that includes a "food chain" of processes and business intelligence. (The linked file is several years old.)

 
At 26 June, 2007 20:58 , Blogger J said...

Hey, you have a great blog here! I'm definitely going to bookmark you!

I have a Idiot Proof Diet site. It pretty much covers dieting related things.

Come and check it out if you get time ;)

 

Post a Comment

Links to this post:

Create a Link

<< Home