Skip to main content

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

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

Four Service Characteristics

Recently I came across several articles by researchers and experts that laid out definitions and characteristics of services. ITIL provides us with a definition that can help drive the creation of value-laden services: A means of delivering value to customers by facilitating outcomes customers want to achieve without the ownership of specific costs and risks. An area that ITIL is not so clear is in terms of service characteristics. Several researchers and experts put forth that services have four basic characteristics (IHIP): ·          Intangibility—Services are the results of actions not things. They have no physical presence and represent a logical set of elements. One way to think of service is “work done for others.” ·          Heterogeneity—Also known as “variability”; services are unique items because of the mechanisms used to deliver services-that is people. Because the people element adds variability, the service is variable. This holds true especially for th

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