Skip to main content

The ITIL Practitioner – Relevant and Required Today

What are the challenges that every CIO, CEO or service provider faces? EVERY Service provider today must move BIGGER, BETTER, MORE… FASTER than ever before and do it at the LOWEST COST possible! We used to speak about the rate of change and yes that is still increasing. The rate of change is only one of many aspects that present challenges that must be considered, others include:

Dynamic Business Requirements - We do not even get started with the deployment and the requirements are changing. This can no longer be an excuse for overruns. The service provider must expect this and have the people, process and technology in place to respond quickly to these expected changes.

Transformational Change – A transformational change is designed to be organization-wide and is enacted over a period. Transformational change and this culture shift will result from a change in the underlying strategy and processes. This includes strategic transformations for DevOps initiatives, Agile or the embracing of ITIL Best Practices.

Digital Transformation – Including Artificial Intelligence / Machine Learning, The Internet of Things, Natural Language Processing, Robotic Process Automation, Virtual Reality and the list goes on…

More than ever before the need for a systematic approach, skilled practitioners, and a mission to succeed is needed for all service providers. The ITIL Practitioner must go even further and strive to go beyond to produce a methodical way to use Best Practices for introducing new or changed services and processes into your culture. 

The ITIL Practitioner will need in-depth understanding for:
  • The need for Continual Service Improvement (CSI) and then how to make the CSI Model intrinsic to the organization. 
  • Leading, inspiring, and motivating people throughout to take real action for the Management of Organizational Change. 
  • Facilitation, collaboration and communications that benefit all stakeholders. 
  • Instilling a culture of measurement with metrics that produce real value and outcomes that matter. 
Practitioners in IT and partners on the business side of the organization must understand the true value of well-designed and delivered services and then work together to achieve them. This is REQUIRED to achieve strategic outcomes for any transformation.
ITIL® Practitioner Guidance – the ITIL Practitioner course goes beyond the what and the why and provides practitioners a methodical way towards real success!

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…