10 January 2010

Contextually Relevant Experience & Why It Matters

Imagine what would happen if you went to a doctor (or any specialist) who had no experience in your specific condition or situation.  Has this every happened to you?  It has to my family when I was young.  Let me tell you, it wasn’t pleasant.  What was frightening was that the “professional” didn’t know that they didn’t have the right experience.  What was just as bad was that my family didn’t have the knowledge or experience to know that the person we went to was not qualified.

This is a situation encountered by many organizations when seeking advice and/or appraisal services from a CMMI consultant / appraiser.  However, in business, you should at least know enough about your organization and ways of operating to do your homework before picking someone to help you with CMMI.

What you may not have known is that CMMI and the appraisal method are not as clear and obvious as other means of performance evaluation and that you must choose your consulting firm and appraiser very carefully, and among other factors, consider their contextually relevant experience. . . .

Labels: , , , , ,

27 December 2009

Picking a Lead Appraiser: "Dammit, Jim! I'm a doctor not a bricklayer."

In this quote, CAPT Kirk wants Dr. Bones McCoy to do something he feels he's not-qualified to do because he doesn't know how to treat the species.

  

I'm using it to explain that organizations looking for a lead appraiser to work with them towards an appraisal and/or to perform an appraisal ought to think of what we do as they would think of a doctor, not a laborer or vendor. 

Do you really want the lowest price doctor?

For that matter, is the highest price doctor necessarily the best in town?

When reaching out and interviewing for a lead appraiser or CMMI consultant, you:

    • Want the person who is the right person for the job.

    • Want someone who is qualified (definitely not under-, but preferably not over- either).

    • Not the lowest bid.

    Seriously, whoever you hire for this effort has in their power the ability to make or break your future.  They literally have the health and well-being of your organization in their hands.  They can put you in the dump just as easily as they can take you to the next level.

    They should see themselves that way as well. 

    Unfortunately I've got too many sad stories of appraisers/consultants who definitely see that they can make or break you, but they don't feel like they personally own the responsibility for what happens to you when they're done. 

    If it costs too much?  So what?  
    If you get no value?  Not their problem.  
    Didn't see any benefit?  Didn't learn anything?  Things take longer and cost more and you're not seeing internal efficiencies improve?
    YOU must be doing something wrong, not them.

    In an AgileCMMI approach, your CMMI consultant and/or lead appraiser would see themselves as and act like a coach, and would put lean processes and business value ahead of anything else.  And, an AgileCMMI approach would know that when the processes work, they add value; when they add value people like them and use them; when people like and use them, the next “level” is a big no-brainer-nothing.  You get it in your sleep.

    Let me know if you want help finding the right lead appraiser or consultant.

    Labels: , , , , , , , ,

    20 December 2009

    Worse than Worthless . . .

    Your people with prior CMM/CMMI experience are probably worse than worthless, they'll probably cause you to fail.

    Why?

    Because what they (or you) think they (or you) know is probably wrong and the advice you’re getting, the expectations being generated are entirely off base.

    It all goes back to the many ways in which CMMI can be done poorly and the few, simple, but hard work ways in which it can be done correctly.

    Every time I meet with a new prospect I’m confronted with reams of inaccurate assumptions and assertions about what it will take to implement CMMI and how am I expected to “do all that” and still claim to be “agile”.

    My simple answer: I’m not going to do all that.  And, you shouldn’t be doing it either.

    Seriously, you’ve got to wonder about executives who will force their company into doing stupid things for the sake of a rating instead of doing their homework to learn about CMMI before they head out on an implementation journey.

    A recent client didn’t know any better.  They hired a consultant and an appraiser to evaluate their work against CMMI and to help them prepare for a SCAMPI appraisal.  Unfortunately, they got as far as the appraisal only to realize they weren’t going to get the target Maturity Level.  (I won’t get into some of the inappropriate behavior of the firm they hired.)

    However, when this client was confronted with:

    1. Do something stupid, or
    2. Find a better way to do something smart.

    They took option B and found a consultant and an appraiser who understood their context and found how to both be on a disciplined improvement path while also remaining true to their own business.

    Fortunately for them, this client had a strong engineering backbone and knew what they did worked and were confident in their processes.  Many companies have a while before they can claim that much.

    Next week:

    Picking a Lead Appraiser:  "Dammit, Jim!  I'm a doctor not a bricklayer."

    Labels: , , , , , , , ,

    13 December 2009

    Everything you thought you knew about CMMI is (probably) wrong.

    What most people (80/20) seem to "know" about CMMI and the SCAMPI appraisal method comes from what people learned and how they used CMM and CMMI in the early adoption phase.

    However, instead of innovating and using engineering to create appropriate processes, they just reused old and often poorly-fitting processes and approaches to situations they never dreamed of in the 1980s.

    Even people with positive experiences with CMM/CMMI tell us that we challenge what they once believed to be “true” of CMMI … but that they’re relieved because many always felt that what they thought was “true” made little sense.

    Recommend:
    Next week: 

    Your people with prior CMM/CMMI experience are probably worse than worthless, they'll probably cause you to fail.

    Labels: , , , , , , , , , ,

    20 June 2009

    Top 10 Clues You're Not Ready for a SCAMPI

    10. Four months ago you couldn't spell "CMMI".

    9. No one in your organization has ever had any training of any kind whatsoever in CMMI, appraisal planning, or process improvement.

    8. You haven't worked with anyone (in-house or hired) who knows what they're doing with CMMI.

    7. Price-shopping for lead appraisers seems like a good idea. Kind-a like price shopping for a heart-surgeon.

    6. After months of work, you switch from one constellation to another and think your appraisal is still on schedule (see #9 and #8). Kind-a like switching your team from field hockey to ice hockey mid-season.

    5. Your CEO is petulant about the delay of your appraisal yet has no idea that your actual process performance is in the toilet.

    4. You've waited until it's time to start planning for your SCAMPI to start looking for a consultant to help you implement CMMI in an "agile" way.

    3. The only people you're sending to Introduction to CMMI are the ones you plan to have on the appraisal. You have no back-up plan if they can't make it to training and/or to the appraisal. Class isn't for another month, and, they're the same ones who've been working on your processes for the past several months, but until now, see #9 and #8.

    2. You haven't qualified the people in #3 with your lead appraiser (which you haven't hired yet + see #9 and #8), you haven't qualified the projects to be appraised with your lead appraiser (which you haven't hired yet + see #9 and #8), and nonetheless, you have established a level of effort for the appraisal despite all of the above.

    And,

    The Number One Clue You're NOT Ready for a SCAMPI:

    1. After months of work, you still don't see there's a fundamental flaw in committing to or expecting others to commit to (including your appraiser no less!) a firm-fixed price contract without knowing the requirements.

    I wish the above list of clues were tongue-in-cheek.


    Sadly, it's not. There is, nonetheless, plenty of fiction in it:

    • The order of the list is mostly arbitrary.
    • The list is not scientific.
    • The list really should be longer. A lot longer.
    • These clues are just from my experience alone, and doesn't account for anyone else's, so it's pretty idiosyncratic.

    While in many cases, any one of the items in the list of clues could easily sabotage an organization's process improvement effort (let alone an appraisal), one thing that makes it especially troubling is the preponderance with which I encounter a single organization exhibiting most or all of these clues! And yet, such organizations think they actually can dictate to their lead appraiser the terms and conditions and the readiness of their organization to be appraised!

    I tried to limit the clues to only things you could pick-up from a conversation -- even if you know nothing about CMMI or the SCAMPI appraisal method. I tried to keep the clues to things that don't have to do with CMMI itself or process stuff as a general theory. If I had included such items, I would add:

    • You don't know that to do a SCAMPI you actually have to have used the processes on actual projects.
    • You don't realize that there's more to CMMI than the names of the process areas.
    • You don't realize that the generic goals and practices aren't just "extra information".
    • You don't know that it's still the lead appraiser's responsibility to approve the people and the projects to be in the appraisal.

    If you look at some of the other behaviors of organizations not really ready for a SCAMPI, you'll find that they continue to:

    • accept more work than they can handle,
    • be unpredictable in what they will deliver and when,
    • measure little other than billable hours, and
    • have no insight into where their defects come from.

    Despite the condition in which many organizations may have artifacts for an appraisal, they have seen no intrinsic benefits to their new set of processes. They've been just "chasing a level", which results in lots of work for no real benefit. You can guarantee these organizations will drop their processes shortly after the appraisal.

    Really, what these clues point to is the dreadful lack of realization that first and foremost, process improvement requires the right culture for process excellence. The above list points to a fundamental absence of the culture for process excellence. What people don't realize (especially in the USA), is that process improvement is a total JOKE for companies with the right culture of process excellence. If people want the truly idiot-proof, guaranteed, easy path to just about any CMMI Maturity Level, they would need to go no further than to foster a culture of process excellence, then whatever they did from that point forward would likely cause just about every practice in CMMI to form on its own. In other words, these clues aren't about process, they're about culture and leadership. You don't have to know anything about CMMI to pick up clues about culture and leadership.

    One of the failures of CMMI is that it fails to press the basic importance of culture and leadership for process improvement. It fails to communicate in no uncertain terms that an absence of the right culture (and what that looks like) and the absence of leadership (and how that shows up) will lead to a failure in process improvement -- CMMI or otherwise. I'm not blaming CMMI for not including this information in the text, because much of it is there. What I'm saying is that despite what is there about the importance of culture and leadership, most CMMI users fail to grasp these important points. The text, therefore, fails to communicate this in a way that people will pay attention.

    CMMI should come with a warning similar to, "Don't Try This At Home!" or "Use Only as Directed!", or "Check with a Qualified Professional Before Beginning Any Process Improvement Program", or "You Must Be *This* Tall to Use this Book". Or simply, "Danger Ahead!". Something to get people's attention and direct them to some of the fundamentals of any improvement program.

    This accusation is not just leveled at garden-variety CMMI adopters. Often, they're the hapless "stuckees" forced to "make CMMI happen" against all odds. At least there's ample reason to be sympathetic to their plight. What's inexcusable are the too-many consultants, instructors and appraisers who are willing to ignore these fundamental requirements-for-success and who are unwilling or unable to posture with prospects and clients in such a way as to impart the importance of culture and leadership to success with CMMI. So, that translates to a pathetic statement about the consulting abilities (and possibly the ethics) of too many people who take money to work with others on CMMI.

    Sorry for the rant. But people need to be warned. Attempting a CMMI effort without the requisite culture and leadership attitude may yield a short-term appraisal rating, but will ultimately lead to medium and long-term failure. *THAT* I can guarantee.

    This is why I'm such an advocate for agile methods. Agile methods impart some of the basic needs for long-term process success. And, it imparts them at a level of abstraction usable by people who aren't process experts, yet establishes many of the appropriate culture and leadership traits that so many CMMI-only efforts fail to recognize. Agile values, methods, and practices empower their teams, cause leadership to eliminate obstacles, value the input of customers and practitioners alike, values learning, develops multi-disciplined teams, and most importantly (as far as processes are concerned) promotes lean thinking. While Agile ideas may not change leadership and culture over night, they contain many of the right activities that can eventually win over those whose hearts and minds need winning over. And, with the appropriate use of CMMI, agile ideas can kick-start the motion and direction needed for long-term and ongoing improvement.

    I'll be writing more about why CMMI and Agile need each other for a while.
    Stay tuned.

    Labels: , , ,