Skip to main content

Process Maturity – How do I measure it?

In order to manage and control processes and services, they have to be monitored and measured. The design of the measurement methods and metrics used to measure process are critical to success and might even be the most crucial element.  In practice we tend to see Critical Success Factors and Key Performance Indicators defined in the process documentation but is anything being done with those?

We not only need to define the metrics for measuring the process but also must ensure that the design and implementation of the process also includes a system for ongoing monitoring, reporting and most important action for continual improvement of the process. Without it the process is destined to fail.

Process designers must assert caution and use wisdom when defining the metrics and measurements for the process.  Careful consideration must be given to how these measurements are going to affect and change the behavior of the practitioners and stakeholders that produce or receive value from this process.  Rest assured that measuring the process will affect people and we must ensure the outcome is one that is conducive to success.  Selecting only measurements that encourage progression towards meeting business objectives or desired behavioral change should be selected.

The process design ensures that we have the capability to improve the process over time.  Think about it.  Is a process ever perfect?  Is the demand from the business ever static in today’s world? The emphasis should be on the quality, speed, and cost in order to meet the dynamic needs of the business and the outcomes of the products and services that service provider delivers.  Therefore, measurement methods and metrics should reflect these requirements and be designed to measure the ability of processes to them.   Be careful though. The process measurements selected need to be appropriate for the capability and maturity of the processes being measured. Immature processes are not capable of supporting complex measurement methods.  ITIL describes four types of metrics that can be used to measure the capability and performance of processes.  You might find these helpful.
  •  Progress - Milestones and deliverables in the capability of the process 
  • Compliance - Compliance of the process to governance requirements, regulatory requirements and compliance of people to the use of the process
  • Effectiveness - The accuracy and correctness of the process and its ability to deliver the ‘right result’
  • Efficiency - The productivity of the process, its speed, throughput and resource utilization. Measurements and metrics should develop and change as the maturity and capability of a process develops. Initially, with immature processes the

Be cautious with these, the first two levels of metrics should be used to measure the progress and compliance of the process initially.    You should ensure that the process is consistent and being followed.  As the process maturity develops, effectiveness and efficiency metrics can be added with an understanding that progress and compliance are still paramount.

Comments

Robin Goldsmith said…
It’s nice to see more insightful discussion about measuring processes rather than mindless maturity model fitting. I’ve found that few organizations actually pay attention to managing and measuring their processes, and seldom does anyone feel it is their responsibility. Instead, the suggested measures mainly are applied to projects without recognizing that one’s process determines how one does projects. Moreover, most organizations are pretty oblivious to meaningful measures of project, let alone process, effectiveness which has to be the primary measure before the other measures are relevant.
Robin Goldsmith said…
It’s nice to see more insightful discussion about measuring processes rather than mindless maturity model fitting. I’ve found that few organizations actually pay attention to managing and measuring their processes, and seldom does anyone feel it is their responsibility. Instead, the suggested measures mainly are applied to projects without recognizing that one’s process determines how one does projects. Moreover, most organizations are pretty oblivious to meaningful measures of project, let alone process, effectiveness which has to be the primary measure before the other measures are relevant.

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: René. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…