Skip to content

CMMI Process Improvement applied to IT systems

September 17, 2008
tags: ,

Living day to day in a process improvement job, it’s easy to quickly lose sight of the big picture; we can’t see the forest because we’re focused on the trees. We tend to see individuals around us making independent decisions and taking seemingly unrelated actions. We get caught up in trying to deal with every separate event using a different approach and frame of mind than the last event. It is also quite easy to lose sight of the relationships between your process improvement work and product or service delivery. Sometimes, CMMI or process improvement takes on a life of its own and we end up doing process improvement for its own sake.

In systems thinking, two systems archetypes that provide a way of gaining a big-picture view of commonly occurring systemic problems in organizations: fixes that backfire and shifting the burden. These two archetypes are particularly useful in understanding and resolving problems that frequently plague CMM and CMMI-based process improvement efforts.

Fixes That Backfire

In the fixes that backfire systems archetype, the “obvious” solutions are applied to problems. However, because the perceived or obvious solution is frequently applied hastily and without a thorough understanding of the problem, the result is often unintended consequences, including a worsening of the problem. The most pronounced example of a fix that backfires is corporate downsizing to improve profits. In one 1991 study of 850 companies that had cut staff drastically, only 41 percent had achieved the savings they hoped for.

illustrates the dynamics of the fixes that backfire archetype as it relates to software and systems process improvement. Because the net, long-term, negative effects of the “fix” are greater than the short-term, positive effects, the reinforcing loop is the prevailing influence in the system. The top loop represents the organization attempting to address the problem of poor software or systems delivery by implementing CMMI-based process improvement. The bottom loop — also known in systems thinking as an “addiction loop” — represents the long-term effects of the “fixes.” When it turns out that process improvement is not the panacea that it is often touted to be, there can be unintended negative consequences.

The fixes that backfire archetype has three primary manifestations in process improvement:

1. The race to achieve a maturity level causes widespread cynicism, which in turn leads to a grass-roots resistance to the process improvement initiative.

2.Process discipline and improvement is done for its own sake and the consequence is that the organization’s software and systems development performance gets worse.

3.The cost and value of process improvement activities are not integrated with the price of things sold to a customer, such as the price of products sold or cost of services rendered. Process improvement — and probably other internal “improvement” initiatives — are viewed as infrastructure or overhead. As these internal initiatives grow, so does the percentage of the organization’s employees whose work does not directly produce something that is sold to or adds value to what is sold to a customer. it becomes increasingly difficult for the expanding organization to achieve and maintain its profit goals because operating costs grow at a faster rate than that of realistically achievable revenue.

The Race to Maturity Levels

Frequently, executive and senior level managers are sold on CMM or CMMI as a vehicle for improving software or systems development and delivery. However, they get fixated on achieving maturity levels under the belief that maturity levels are concrete evidence that processes have improved. The maturity level becomes the evidence that the organization has improved its efficiency, effectiveness, and quality. Such beliefs are as faulty as assuming a student has actually learned something because he received an “A” in class.

Acting on this fixation, the executives will sometimes construct incentives, such as bonus programs for senior and mid-level managers to achieve maturity levels in their respective suborganizations. Now, both level envy and the ensuing race to achieve levels is on! The focus on maturity levels drives people to look for quick fixes that will enable them to “pass” an appraisal. The symptoms — observable behaviors and artifacts — most commonly associated with a race to maturity levels are:

Deadlines are established for achieving a maturity level without any estimating or project planning that supports the deadline (which, by definition, is a low maturity behavior).

The appearance of ridiculous slogans such as “Level 5 in ’05.”

People read CMM or CMMI and learn to recite the model’s terms and phraseology.

Policies and procedures are rapidly created and frequently copy practices verbatim from CMMI.

Project managers, under pressure from upper level management, create elaborate project documentation that satisfies the letter but not the intent of the model. They promptly shelve the project documentation and do not use it to manage their projects.

The problem worsens in a large organization in which various suborganizations are trying to achieve maturity levels independent of each other. The suborganizations’ respective managers too often let their egos and competitive natures get the better of them and try to out-do each other to be the first to achieve the targeted level.

Once organizations have become entrenched in the level race (or perhaps more accurately, “level wars”), they are in the addiction loop of the fixes that backfire system archetype and you can count on rationale and reason being abandoned. The organization takes a short trajectory to the maturity level, which it more often than not achieves — one way or another.

And what of the unintended consequences? Those incentives for achieving maturity levels usually stop at the mid-level manager and almost never make it down to anyone doing the work, including SEPG members and project managers who have done the bulk of the work in the death-march process improvement project. For a time period ranging from two hours to three days following “passing” the appraisal, everyone in the victorious organization is elated and ecstatic. Once the appraisal high wears off, people start looking around for some lasting and meaningful results of their work but, for reasons they can’t always comprehend, everything looks and feels the same as it did before the maturity level race. Now, good luck to executives and senior managers who try to persuade these same people to get excited again about the next maturity level.

Even in extreme command-and-control work environments where the primary motivation is fear (usually of losing your job or being marginalized), these fixes that backfire eventually take their toll on the morale and momentum of process improvement initiatives. Smart, skilled, process-disciplined people start to look outside the organization for more meaningful, rewarding work. Project managers and engineers become jaded on the whole idea of model-based process improvement. They’ll continue giving a gratuitous “salute” or lip-service out of fear of not conforming, but they’ll be burned out on process. Worse yet, they will perceive — perhaps accurately — that the whole CMMI effort is a waste of time and money. Cynicism prevails.

The organization that chases maturity levels for their own sake and fails to set business goals for process improvement will spend hundreds of thousands or even millions of dollars on model-based process improvement and have nothing more than a few gratified egos to show for a ROI. Recent very public situations tell us that greed and ego may not be so in vogue anymore in corporate America.
Process for Its Own Sake

Sometimes, organizations don’t get too wrapped up in CMMI maturity levels, yet process still becomes the be-all and end-all to fixing every issue plaguing the organization. For many of my years in Xerox, “it’s the process” or “fix the process” became the only politically acceptable approach to any problem. The primary fallacy of this approach is that it ignores the observable, measurable fact that there really are people and accountability problems which cannot be resolved by addressing only the process.

A classic example of a backfire from applying a fix occurs when organizations attempt to apply the entire CMMI to traditional IT or sustaining engineering shops. With intelligent interpretation and tailoring, many of the CMMI practices can be applied to improve work in these environments. But the implementation of processes and procedures that are nothing but a regurgitation of CMMI in these environments results in burdening the organization with process overhead that doesn’t add value, thus making the organization less effective and efficient than they were without CMMI.

Strategies for Fixes That Backfire

In planning the process improvement effort, ensure the plans include achieving measurable or observable business goals in addition to achieving maturity levels. Make sure that reporting progress or success includes status against all the process improvement goals and not just the number or percentage of practices satisfied.

Increase awareness, especially among senior and executive managers, of the unintended consequences of chasing maturity levels. In 2001, I was involved in an e-mail conversation with senior level managers and marketing people in BMC who were trying to come up with strategies for countering the “CMM level race” approach of one of their biggest competitors. I sent out a note thinking that it would be career limiting because it went directly against the prevailing beliefs. Much to my surprise, a senior marketer read and understood my note and invited me into further conversations on how we could market real process improvement benefits without getting into level-wars with our competition.

Spend the time understanding the problem. You don’t necessarily have to conduct time-consuming formal root cause analysis, which can often lead to “analysis paralysis,” but you can’t afford to continue applying solutions to symptoms, only to have the root problem perpetuate or worsen.

Establish alliances or relationships with people in your marketing and sales organizations. Find ways to defray some of the cost of process improvement activities by selling (and charging for and collecting!) the benefits of process improvement. With the right approach, a customer or client will be willing to pay a higher price for the goods or services so long as you’ve convinced them that there is greater value.

Shifting the Burden

According to Systems Thinking, shifting the burden …

usually begins with a problem symptom that prompts someone to intervene and “solve” it. The “solutions” are obvious and immediate; they relieve the problem symptom quickly. But they divert attention away from the real or fundamental source of the problem, which becomes weaker as less attention is paid to it …

In this systems archetype, the perceived problem is a lack of process or process discipline in the organization or that the organization does not have a CMM or CMMI maturity level. So the “obvious” solution is to implement CMM or CMMI. In the short term, the fix does appear to address the perceived problem; lack of process is resolved by writing and implementing processes.

The not so easily observed yet insidious effect is that effort and focus shifts from product or service delivery (or integration) to the symptom of inadequate processes, which in turn either does nothing to improve product or service delivery or hurts it by burdening the existing delivery processes with overly bureaucratic standards, procedures, methods, and work products which don’t help.

No comments yet

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: