Skip to main content

Next Steps

In an earlier blog I had talked about the need for organizations to have the ability to measure their processes against those of their competition or some defined industry standard.  Before that could happen, it had to be determined if your processes are mature enough to ensure that you can gather the needed data for a successful undertaking.  

If your assessment calls for developing a new process, reengineering or improving an existing process a sound methodology for that mission could be the “Ten process design and improvement steps” as describe in “The ITSM Process Design Guide by Donna Knapp.The elegance of this approach is that it can be utilized to design or improve any process regardless of maturity level.  It provides the common vocabulary, tools, and techniques needed to engage all participants who would be required for these process and improvement actions.  They help to define and understand the end to end process, who the customers are and their requirements.  It also allows you to levelset the process with your organizational structure, related processes and the available technologies.  It also provides the mechanism to allow for continual process improvement.

The ten process design and improvement steps are grouped into the following four logical phases.

          Requirements Definition-Requirements Definition Document
  1. Determine management’s vision and level of commitment.
  2. Establish project and form project team.
  3. Define process and identify customer requirements

     Process Analysis-Gap Analysis Report
  4. Document the as is process and baseline current performance.
  5. Assess conformance to customer requirements.
  6. Benchmark current performance.

    Process Design and Implementation-Process Definition Document
  7. Design or redesign process.
  8. Solicit feedback, fine tune, and finalize the design.
  9. Implement new design.

    Continual Process Improvement-Maturity Assessments and Metrics
  10. Assess performance and continually improve.

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