Dear Appraiser,
Our CMMI Consultant tells me that all CMMI Practices have to be used on every project with full rigor- regardless of size. That doesn't sound right.
What gives? ~Harley Fullblast
It's important to adjust your Process knobs to the right levels
Dear Mr. Fullblast,
Okay, I’ll admit it — Justin Bieber’s “Baby” sounds amazing on my iPhone.
Wait, did I just say that out loud?
Yes, I did. And honestly? It sounds really good. Now, don’t get the wrong idea — Bieber is definitely not my usual go-to artist. In fact, the only reason I even own a copy is because my 12-year-old niece gifted it to me on iTunes. (Still not sure what I did to deserve that.) But here we are… and I have to say, it sounds fantastic.
Not because it’s my favorite genre, and not even because of the singer. It sounds great because a sound engineer carefully adjusted all the right knobs. The mix is balanced. Nothing is maxed out unnecessarily. Some elements are subtle, others are prominent — all placed with purpose.
Compare that to an old live Pink Floyd recording I have — captured on a handheld cassette recorder in the '70s at Madison Square Garden. Nostalgic? Sure. Sonic quality? Absolutely awful. I don’t remember much from that night, but I know this: those knobs were not in the right places.
CMMI Is Like a Mixing Board
Here’s where this analogy gets fun. The CMMI is a lot like that sound engineer’s mixing board. Only instead of a dozen sliders, we’ve got over 350 “knobs” at Maturity Level 3 — each representing a process area, a practice, or a tool. And like sound engineering, the magic is in how you tailor those settings for each unique situation.
Not every project, team, or organization needs the same mix. Cranking every knob to “11” doesn’t guarantee success — it just creates noise, waste, and frustration. Instead, the art lies in adjusting the process to fit the need. Some practices will be more critical than others, depending on your goals.
That’s right — some practices are more important than others.
Beware the "Whack-a-Mole" Approach
Too often, when an appraisal flags a practice as “partially met,” the knee-jerk response is to reverse-engineer the checklist, bulk up the documentation, and crank up the visibility. Problem solved, right?
Not always.
Sometimes, that perceived weakness exists because of how other “knobs” have been configured. Tweak one area too aggressively, and you might throw everything else out of balance. I call this the Whack-a-Mole approach to process improvement — and it's as chaotic as it sounds.
Myth: “Everyone Must Do Everything the Same Way”
You may have heard some consultants say that Maturity Level 3 is all about strict uniformity:
“Everyone doing everything the same way, every time.”
“More than 54.7% of sample artifacts must be fully deployed!”
“Every practice must receive equal emphasis.”
I disagree. Strongly.
That’s not what the model teaches. In fact, the CMMI training materials and the “Foundations of Capability” class make it clear: Defined Process does not mean a single, one-size-fits-all process. It means creating a flexible framework that supports multiple approaches — tailored to fit context, constraints, and objectives.
Or, to borrow from one of my niece’s favorite movies:
“Defined… You keep using that word. I do not think it means what you think it means.”
Process Knob Placement Determines Success
A smart process architecture isn’t rigid — it’s deliberate. Whether you’re choosing Planning Poker vs. COCOMO, Fagan Inspections vs. informal reviews, or daily standups vs. all-hands meetings, the tools are only as effective as the context they’re applied in.
Where and how you set the knobs determines the quality of your outcome.
It’s the difference between an average project… and a great one.
Want to see what it looks like when the real pros set the knobs just right? Check out this behind-the-scenes video of how audio engineers work their magic on pop vocals: https://www.youtube.com/watch?v=RmT6MDOD3uc
Feel free to leave me a question here or email me at AskMe@broadswordsolutions.com.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.