Skip to main content

Kickstart ITIL 4

ITIL 4 is coming! ITSM Academy is working hand and hand with the experts to ensure you achieve your mission. ITIL 4 Updates will be kept current for you so that you can stay the course. As a Global Strategic Partner of AXELOS (the owners of ITIL) we have been working with their teams, and the global community, to help ensure that ITIL 4 is "worth the wait".

ITSM professionals have the opportunity to expand on the work, effort and skillsets that they gained from ITIL v3 and allow newcomers the opportunity to accelerate their ITSM and transformation initiatives. ITIL 4 will help us all to accelerate our productivity and to integrate Best Practices across the entire organization for real transformation and business value.

ITIL 4 retains the best of ITIL v3/2011, with most of the operational and tactical practices and processes you know. The release also includes focus on integrating many best practice "frameworks". Think DevOps, Agile, Lean, etc. All good news – and long overdue.

Kickstart Your Journey
Prepare NOW for ITIL 4 by becoming a Certified ITIL Practitioner.

Stay the course my friends. As AXELOS rolls out ITIL 4, the timing is great to learn about the current influences and cultural movements directly impacting the updates; including Agile Service Management, DevOps, Lean and Process Design. It is high risk to lose momentum or to abandon the gains we have made with Best Practices. Don’t back off on your education, training and leadership. As an industry, we must keep the momentum going. 

On the ITSM Academy website, we have created a page for ITIL4 updates, feel free to bookmark it and check back in as we progress into 2019. 

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…