Skip to main content

Transition to ITIL 4 – Managing Professional Transition (MPT) - 17 ITIL V3 Credits Required

If you have ITIL Expert Certification or 17 ITIL v3 Credits you are eligible to transition UP! 

The Managing Professional Transition certification classes are filling up quickly, and are only available for a limited to, so we recommend that you grab your seat..."while the getting is good" :-). 

ITIL 4 Foundation is NOT a prerequisite. However, the Foundation course provides exposure to concepts and practices which aren't covered in MPT. The ITIL 4 Foundation Module of MPT will give you a good introduction to the Service Value System, The Service Value Chain, Service Relationships and more. Reach out to the Academy team for your discount on your ITIL 4 Foundation training.

Managing Professional Transition will start you on your journey for new ways of thinking and new ways to approach best practice and like any other bridge or transition class, it has a short shelf life!

The Managing Professional Transition Course covers:

And from the advanced courses:
Watch the ITSM Professor Blogs for an introduction and study tips for each module contained in the Managing Professional Transition certification class. 

Click here to read our blog series on ITIL 4 Guiding Principles.

Start now to earn your “transition” certification while it is available.  Join us to learn new ways of thinking and working to enable you to successfully navigate in the modern digital world.

...educate & inspire

Download ITSM Academy's ITIL4 Training Catalog

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…