Process Maturity Framework (PMF)

Process Maturity Framework (PMF) - Part 1

I am often asked about the best way to measure process maturity. While there are several process maturity models available, I prefer the “Process Maturity Framework” (Appendix H pg 263) from the V3 ITIL Service Design Book. You can utilize this framework to measure your Service Management processes individually or Service Management as a whole.

The five areas that the assessment should focus on are:

Vision and Steering
Process
People
Technology
Culture

The major characteristics of the Process Maturity Framework (PMF) are the following:

Initial (Level 1)
The process has been recognized but there is little or no process management activity and it is allocated no importance, resources or focus within the organization. This level can also be described as ‘ad hoc’ or occasionally even ‘chaotic’.

Repeatable (Level 2)
The process has been recognized and is allocated little importance, resource or focus within the operation. Generally activities related to the process are uncoordinated, irregular, without direction and are directed towards process effectiveness.

Defined (Level 3)
The process has been recognized and is documented but there is no formal agreement, acceptance or recognition of its role within the IT operation as a whole. However, the process has a process owner, formal objectives and targets with allocated resources, and is focused on the efficiency as well as the effectiveness of the process. Reports and results are stored for future reference.

Managed (Level 4)
The process has now been fully recognized and accepted throughout IT. It is service focused and has objectives and targets that are based on business objectives and goals. The process is fully defined, managed and has become proactive, with documented, established interfaces and dependencies with other IT processes.

Optimizing (Level 5)
The process has now been fully recognized and has strategic objectives and goals aligned with overall strategic business and IT goals. These have now become ‘institutionalized’ as part of the everyday activity for everyone involved with the process. A self-contained continual process of improvement is established as part of the process, which is now developing a pre-emptive capability.

Comments

The Four Ps of Service Design - It’s not all about Technology

People ask me why I think that many designs and projects often fail. The most common answer is from a lack of preparation and management. Many IT organizations just think about the technology (product) implementation and fail to understand the risks of not planning for the effective and efficient use of the four Ps: People, Process, Products (services, technology and tools) and Partners (suppliers, manufacturers and vendors). A holistic approach should be adopted for all Service Design aspects and areas to ensure consistency and integration within all activities and processes across the entire IT environment, providing end to end business-related functionality and quality. (SD 2.4.2) People: Have to have proper skills and possess the necessary competencies in order to get involved in the provision of IT services. The right skills, the right knowledge, the right level of experience must be kept current and aligned to the business needs. Products: These are the technology managem

What Is A Service Offering?

The ITIL4 Best Practice Guidance defines a “Service Offering” as a description of one or more services designed to address the needs of a target customer or group . As a service provider, we can’t stop there! We must know what the contracts of our service offering are and be able to put them into context as required by the customer. Let’s explore the three elements that comprise a Service Offering. A “Service Offering” may include: Goods, Access to Resources, and Service Actions Goods – When we think of “Goods” within a service offering these are the items where ownership is transferred to the consumer and the consumer takes responsibility for the future use of these goods. Example of goods that are being provided in the offering – If this is a hotel service then toiletries or chocolates are yours to take with you. You the consumer own these and they are yours to take with you. Note: Goods may not always be provided for every Service Offe

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

Search