Skip to main content

Designing and Documenting a Process

Designing and documenting a process enables an organization to move from the initial level of the ITIL Process maturity Framework (PMF) through the repeatable level to the defined level.  To undertake this task without adequate resources can be quite daunting especially given the fact that it must
  • Identify needed changes to job descriptions
  • Develop and document work procedures
  • Identify work requirements
  • Establish the data to be collected and the format to report accomplishments
  • Document the necessary vocabulary to be utilized within the process
The following ten process design and improvement steps can be used to create an easy to use and repeatable approach to help move your organization from one level to the next.  The ten steps are grouped into four phases.  Each phase will produce a deliverable that serves as an input to the follow phase.
Phase: Requirements Definition.   Output: Requirements Definition Document.
1.   Determine the management’s vision and level of commitment
2.   Establish a project and form a project team
3.   Define process and identify customer requirements
Phase:  Process Analysis. Output: Gap Analysis Report
4.   Document “as is” process and baseline current performance
5.   Assess conformance to customer requirements
6.   Benchmark current performance
Phase: Process design and Implementation.  Output: Process Definition Document
     7.   Design or redesign process
     8.   Solicit feedback, fine-tune, and finalize the design
     9.   Implement new design
Phase: Continual Process improvement.  Output:  Maturity Assessments and Metrics
    10.  Assess performance and continually improve
Source:  The ITSM Process Design Guide

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…