Skip to main content

Process Maturity Framework (PMF) - Part 2

In one of my previous blogs I wrote about the ‘Process Maturity Framework”. (Appendix H pg 263 from the V3 ITIL Service Design Book). I mentioned that you can utilize this framework to measure your Service Management processes individually or your Service Management program as a whole. 

With this discussion I would like to speak to the five areas that the assessment should be completed against at each level. The five areas are:
  • Vision and Steering
  • Process
  • People
  • Technology
  • Culture 
Initial (Level 1)
  • Vision and Steering:  Minimal funds and resources with little activity. Results temporary, not retained. Sporadic reports and reviews.
  • Process: Loosely defined processes and procedures, used reactively when problems occur. Totally reactive processes. Irregular, unplanned activities.
  • People: Loosely defined roles or responsibilities.
  • Technology: Manual processes or a few specific, discrete tools (pockets/islands).
  • Culture: Tools and technology based and driven with strong activity focus.
Repeatable (Level 2)
  • Vision and Steering: No clear objectives, irregular unplanned activities, reporting and reviews. Funds and resources available.
  • Process: Defined processes and procedures. Largely reactive process. Irregular, unplanned activities.
  • People: Self-contained roles and responsibilities.
  • Technology: Many discrete tools, but a lack of control. Data stored in separate locations.
  • Culture: Products and service-base and driven. 
Defined (Level 3)
  • Vision and Steering: Documented and agreed formal objectives and targets. Formally published, monitored and reviewed plans. Well funded and appropriately resourced. Regular, planned , reporting and reviews.
  • Process: Clearly defined and well-publicized processes and procedures. Regular, planned activities. Good documentation. Occasionally proactive process.
  • People: Clearly defined and agreed roles and responsibilities. Formal objectives and targets. Formalized process training plans.
  • Technology: Continuous data collection with alarm and threshold monitoring. Consolidated data retained and used for formal planning, forecasting and trending.
  • Culture: Service and customer oriented with formalized approach. 
Managed (Level 4)
  • Vision and Steering: Clear direction and business goals, objectives and formal targets, measured process. Effective management reports actively used. Integrated process plans linked to business and IT plans. Regular improvements, planned and reviewed.
  • Process: Well-defined processes, procedures and standards, included in all IT staff job descriptions. Clearly defined process interfaces and dependencies. Integrated Service Management and systems development processes. Mainly proactive process.
  • People: Inter- and intra-process team working. Responsibilities clearly defined in all IT job descriptions.
  • Technology: Continuous monitoring measurement, reporting and threshold alerting to a centralized set of integrated toolsets, databases and processes.
  • Culture: Business focused with an understanding of the wider issues. 
Optimizing (Level 5)
  • Vision and Steering: Integrated strategic plans inextricably linked with overall business plans, goals and objectives. Continuous monitoring, measurement, reporting alerting and reviews linked to a continual process of improvement. Regular reviews and or audits for effectiveness, efficiency and compliance.
  • Process: Well-defined processes and procedures part of corporate culture. Proactive and pre-emptive process.
  • People: Business aligned objectives and formal targets actively monitored as part of the everyday activity. Roles and responsibilities part of an overall corporate culture.
  • Technology: Well-documented overall tool architecture with complete integration in all areas of people, processes and technology.
  • Culture: A continual improvement attitude, together with a strategic business focus. An understanding of the value of IT to the business and its role within the business value chain.

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 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…