Skip to main content

The Recipe of Best Practices

Implementing the guidance provided by ITIL is very much like cooking. If you have ever cooked something using a recipe (even if it is the directions from the package) you know that although you can vary somewhat from the recipe or directions, you cannot change the recipe substantially and expect the stated results. When cooking cakes or sweets, if you add too many eggs or too little oil or too much sugar or leave out an ingredient, what will result will probably not be what you intended. Recipes (and package directions) are best practices just like ITIL. Package recipes especially have been formulated to achieve the optimal results each and every time you make the food. But we must follow the recipe to get the results.


This is not to say you cannot adjust (or “adapt”) the recipe based on your own tastes or even serving suggestions from the package. Adjusting or adapting does not mean rewriting the recipe or completely ignoring the package directions because you do not agree or like the way the original creator wrote the recipe or directions. Adjusting or adapting means fine-tuning the existing recipe (to make it slightly sweeter or more crumbly) or adding other elements to the final product to make it suit your tastes or dietary restrictions. We must remember that the recipe is the recipe. If we want to bake biscuits we must use a biscuit recipe, not a brownie or cake recipe.
Adjusting and adapting ITIL must be thought of in the same way. We may not like what the best practices tell us we must do or even how we must do it. However, if we decide we are going to rewrite the processes or change the way we design services or how we determine our Configuration Items, then we should not expect the results intended with the best practices. It is a classic case of “wanting our cake and being able to eat it too.” We cannot remake best practices to suit our desires and expect optimal results. We cannot effectively manage and control changes using a demand management process.
I have encountered numbers of implementers who want all the benefits, enjoyment and success that ITIL makes possible. However, they want to rewrite best practices because the effort of doing things as ITIL states is “too painful” or “too theoretical” or “not reality”. We must keep in mind that we make our reality, rather than our reality making us.
What brings many people to ITIL and ITSM is the desire to do things differently or to get better results. These goals require that you “adopt” the recipe and “adapt” to fine-tune to your needs.  When implementing ITSM and using ITIL you must be ready to accept the best practice guidance if you want to enjoy the full satisfaction that those “recipes” can provide.

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…