Overall, “maturity” is a hot topic these days. In fact, my organization just conducted a massive overhaul of IT infrastructure based on the premise that we were not ‘mature’ in basic services across the board. We not only made that statement of ourselves but for each of the major “customer” organizations we serve. It became the basis of seeking outside support to transform our IT infrastructure using a combination of consolidation and outsourcing in the attempt to buy mature practices and processes.
In the case of IT Infrastructure, we used ITIL (Information Technology Infrastructure Library; http://en.wikipedia.org/wiki/ITIL ), which is pretty much the de rigueur for the infrastructure crowd. Of course, you cannot even begin to discuss maturity models without getting into CMMi, which is the grand-daddy of them all (http://www.sei.cmu.edu/cmmi/general/index.html ). But CMMi “can seem to be overly bureaucratic, promoting process over substance.”1 And then there’s COBIT, which provides a framework for best practices for IT practitioners (http://www.isaca.org/ ). I will not try to describe our favorite here (OPM3) other than to say that it is a worthy newcomer, which has yet to show its metal. And there are many more created and cultivated for professional use only (or exploitation, depending on your view).
There are difficulties in showing direct value for maturity programs, but hey, that never stopped those marketing guys, right? Let’s go with the assumption that more mature practices have a chance of making the business a better place and move on to the hard question, which is “What team do I want to back?” I think the answer lies in what you want to accomplish or more importantly, what are your strategic objectives? I know this part should provide some “fire” in the discussion, but in a very short, narrow view, ITIL is for infrastructure, CMMi is for software development, COBIT is for operational applications, and OPM3 is for organizations that are driving lots of change (and therefore projects) in their whole environment. (OK, start shooting!)
So, you really have to have an understanding of the business strategy, culture and organizational structure to determine how to map a maturity model. Unfortunately, most maturity models do not really address strategy, culture and organizational structure, other than to say, “You should have some”. Most models, because of the heritage from CMMi are myopically focused on the processes and the attempt to reach continuous improvement. They forget that organizational environments are quite different and their desires and objectives are quite different (just like people). We need a model that is able to adapt to organizational context as a precursor to the assessment.
I recently came across a model which ties the OPM3 context to the Organizational Strategy, in a way that finally gives executives something to hang on to for their purposes and also allows the translation of Project-Program-Portfolio processes into Operational needs. Attached is a simple depiction of what is described in detail in the book “Executing Your Strategy, How to Break it Down & Get it Done”, by Mark Morgan, Raymond Levitt and William Malek. It shows the context in which effective strategy is defined through the understanding and definition of organizational “Ideation” (defining of purpose, identify and intention), Vision (defining goals and metrics), and Nature (defining culture and structure). Engagement occurs through the interaction of strategy and portfolio management, which then leads to Synthesis (program and project management), which then drives Operations through transition processes. OPM3 clearly fits in the Synthesis and Transition activities and has tried to position itself for the set of Engagement activities. But what has been missing is the context for Strategy, which is the Ideation, Nature, and Vision. Project Management (and therefore Organizational Project Management) is a change mechanism, so it must provide a feedback loop to the Nature and Vision parts of Strategy, and either provide an alignment or change them.
Here are the authors’ six imperatives of strategic investing:
Strategy-Making Imperatives
Ideation: Clarify and communicate identity, purpose and long range intentions.
Nature: Align the organization’s strategy, culture and structure.
Vision: Translate long-range intention into clear goals, metrics and strategy.
Project Leadership Imperatives
Engagement: Engage the strategy via the project investment stream.
Synthesis: Monitor and continuously align the project work with strategy.
Transition: Transfer projects crisply to operations to reap the benefits.
I will conclude this piece by defending OPM3 again. The biggest criticism stems from it being big and complex with its breadth of capabilities. I think it is our jobs to find ways to present it in simpler terms that help others see the core aspect. This means we need to do more to improve the practice and show greater business value. I think it has come a long way and we have all invested ourselves in it. Now is not the time to give up.
Footnotes:
(1) http://en.wikipedia.org/wiki/Capability_Maturity_Model