30 May 2008

Writer gets ink...

I got some ink in today's BBJ.  bbj_logo

Thanks to the DoD's Base Realignment and Closure initiative, Maryland is getting a lot of new Federal jobs and opportunities.  Naturally, I wanted companies looking to capitalize on this to know that if they want to play in the "development" space, that they'd need to know about CMMI.  Readers of this space may be surprised to learn that even in Federal-funding-rich Maryland, not everyone developing technical products (including software) knows that CMMI exists, let alone knows what to do about it.

Originally, I submitted an article about the importance of knowing about CMMI for any company looking to enter this market space.  The folks at the BBJ couldn't wrap their heads around it and asked for something more basic.  This is the result.

At least they published my gmail account as shown.  That way some savvy readers will see the hint.



Here's a print-out of the full article.

Labels: , ,

21 May 2008

I'm about to say something cliché...

... Expect to learn all the time, and you will learn.

I'm working with a great client in Connecticut.  A referral thanks to Bob Lewis.

First off, over coffee Bob unknowingly gave me a new set of metaphors for a topic he admits to having little understanding of: CMMI.

To spare you the details of what he said and how I processed it, please allow me to simply explain the gist.  In CMMI there are lots and lots of things called "practices".

Many people interpret these practices as though they are processes, or worse even, procedures, and they execute the practices mechanically.  Yes, that's usually because these same people either (a) are chasing a maturity level rating, or (b) simply don't understand how to use the model to reap the greatest benefit, or often, (c) both a & b.

Here's how to actually and properly use the practices in CMMI:

They are underlying motivations.

When you think of what doctors, lawyers, athletes and performers do, they practice their art.  And it's a practice because they're constantly applying, learning, adjusting, and responding to the non-ideal and unpredictable conditions presented to them in real-time.  If they were simply following procedures every time, they'd fail most of the time.  Yet, they practice, practice, practice, so that when it comes time to perform the practice they aren't worried about following pre-determined procedures because they must be able to respond to what's thrown at them in reality.  The procedures assume a pre-determined situation and the responses to procedures are ideal to those situations.  What they're exactly doing in real-time comes from their practice, but doesn't necessarily look exactly like what they did last time.

Procedures are good when all the inputs are controllable.  Processes help know what major transformations an object or an idea must go through to become an outcome.  Processes generally follow an expected sequence, but what happens inside the process should have enough flexibility to be rearranged to meet the needs of or to normalize the input conditions.  What the procedures must do, however, is respond to reality.  The way in which procedures inside a process respond to reality to become rearranged or redefined based on the principles and motivations of practices; which are not necessarily even explicit.  They're "just there".

For example, at the process level, a doctor goes through several steps prior to, during and after performing surgery, (e.g., consult, exam, test, analysis, advise, prepare, communicate, operate/investigate, clean/close, protect, follow-up...). Each of these sub-processes to the process may have certain procedures, but each of those procedures is contained within at least one practice.  The practice may not even be written, or formal, but they're certainly part of what the doctor is trained to do based on principles and motivation.  These principles and motivations are taught and refined over time, with practice.  And true, some practices can be beyond the capability and/or maturity of some people.

It's no wonder when an organization's true underlying motivation is the shallow ceremonial decoration of a rating that their results are equally shallow despite the time, energy and money that went into the production effort to pull off ceremonial decorations. (Think: big, gaudy, wedding where everyone knows the couple won't last.)

While learning this lesson, Bob pointed out that what he and I do for a living are, in fact, practices (i.e., consulting practices) and the next morning I find myself before a cozy crowd of client staff and despite having thought through much of how things would go, I still felt like I was winging most of it.  In reality, in real-time, I *was* winging it.  I was responding to the reality, but was never out of my element because I was still.... practicing.  Following the basic principles and motivations to achieve an outcome.

So it all worked out and everyone was pleased.  We made a lot of progress and then I learned the next lesson in this 24 hour period of time: It's really a lot of fun to actually be on the sharp end of the stick once in a while... actively blending Scrum and the immediately useful bits of CMMI.  The real lesson, though, was in gaining re-enforcing validation as I witnessed this organization actively absorb and propose process ideas.  There was no push-back.  Quite the opposite.  Processes were being embraced as one of the things that would lead them towards success.  The alternative would be a slow dissolution of the company.

Once in a while it's nice to really see just how effective blending good ideas can be when this process stuff is put into context of what must be done to succeed.  It just demonstrates again that too many organizations are using CMMI for the wrong reasons made worse by a lack of practice.

Labels: , , ,