Process Maturity Framework (PMF)

Process Maturity Framework (PMF) - Part 3

The professor was recently asked:

"I am having difficulty communicating the business risk of having processes like Change Management and Incident Management sit at Initial (Level 1) maturity. Can you address some of the common business risks and costs companies see by having immature processes?"

Great question! Many organizations do not recognize the inherent risks inhaving immature critical processes such as Incident Management and Change Management. Both processes strive to increase service availability either by identifying and mitigating risk before a change is made or minimizing the impact of a failure after a service is deployed.

To refresh our memories, I have included a description of each aspect of Level 1 in the Process Maturity Framework, with its associated risks:

Vision and Steering: Minimal funds and resources with little activity. Results temporary, not retained. Sporadic reports and reviews.

No formal objectives and targets. Wasted activity with no defined direction for CSI. Reports are not regular nor reviewed and funding for planned growth and resource utilization cannot be determined.

Process: Loosely defined processes and procedures used reactively when problems occur. Totally reactive processes. Irregular, unplanned activities.

Processes are not clearly defined with goals and objectives which can be measured for achievements, customer satisfaction, and alignment with business goals and objectives. Service provider is not delivering value for money and if you are, you cannot show it.

People: Loosely defined roles or responsibilities.

No clearly defined roles and responsibilities. No one will be clearly accountable or responsible for the delivery, support, documentation, maintenance and CSI of services, processes or the underlying infrastructure.

Technology: Manual processes or a few specific, discrete tools (pockets/islands).

Data about your environment and the changes or weaknesses within it are not being captured. Event, alert, incident and problem management not being recorded and intergraded along with the data that will allow your organization to make informed decisions on how to improve your environment and where to wisely spend and budget your resources.

Culture: Tools and technology based and driven with strong activity focus.

We move from a tools and technology focus to a holistic approach of delivering services that meet the needs of business and customer requirements. We focus on delivering utility and warranty thus providing value to the business we support.

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