Quiz Questions Flashcards
Define briefly what a “Stakeholder” is in terms of ITIL and give two examples
A stakeholder can be the supplier, owner of a business, or anyone involved in a process that provides an important role in the operation of a business or exchange of a service.
What is a “best practice” in the context of ITIL?
A best practice is the performing of an action that is tried and true to be known to work extremely well without fail. This is tested by organizations or academics with some sort of valid credential behind them, not always just someone you know (as this could just be a bias). Best practice is similar to ‘good practice’, except good practice kind of assumes that it can’t improve.
There are two types of “needs” a customer has when they are interacted with. Explain both of these using an example scenario.
A customer has an emotional need and a rational need.
You are dealing with a very irate customer.
Explain how you could approach this situation to help diffuse it and work towards the most successful outcome, listing at least 3 techniques.
My dumbass answer that got me marks:
I would first make sure to listen to their situation and try to acknowledge the problem. I would then make sure that I understand their feelings and prove to them that I understand how they feel, and try to relate to them. I would then act on this and come up with a solution. This is the LAURA technique. The first, peak, and ending impressions are just as important. When I first greet the customer I would make sure to be kind and attentive, with a smile. I would ask their name and get the full story. During the whole process I would stay calm and try my best to make them feel that I’m helping and just treating them as a human. I would make sure to end the interaction on a good note, if I couldn’t solve the problem I would give them contact information for someone who could, and make sure that they leave in a better mood than what they came in with. Making sure that I’m not multitasking and giving them my full attention is necessary as well.
Just remember some of these damn techniques
What is the difference between a Service Owner and a Process Owner in ITIL?
A service owner is responsible for:
- efficient monitoring and reporting
- they hold most of the accountability
- They are the first point of customer contact for service related issues
- they look for areas or improvement
A process owner
- look for improvement opportunities
- they create process design
- they provide good training and critical communication or crucial information
- they complete many tasks for the process
You are working in an IT position at a small manufacturing company where the IT department is just the manager, yourself, and a student that works part time.
You are responsible for walk up assistance, phone calls, and answering emails that come in to the IT email address.
What techniques in customer service could you make part of your routine that would improve the interaction with the customer?
I would always ensure to answer the phone with my name
Take notes or make sure that we have some sort of ticketing system so nothing/no one gets lost
Ask for help from the manager when need be, the customer needs to be happy and if that requires me asking for help then so be it
I cna teach the part time student simple things like password recovery to help
For the phone I can add a recorded message with wait times (assuring I can beat those wait times)
If there were long lines I would make sure to wind the line so it felt a little shorter, so the customers weren’t all in one straight line
I always would be attentive, and use the LAURA principle
For the Knowledge Management activities in the Service Transition phase of the ITIL Lifecycle, there is the concept of the “DIKW” model. The first part of that model is Data. What are the other parts? What is the difference/relationship between them?
Given an example to illustrate your explanation.
Data
Information
Knowledge
Wisdom
For my example in class I used the stop light. Data would be RED.
Information would be the stop light is RED
Knowledge would be the west facing stop light at the corner of Charles St and King St is RED
Wisdom would be I need to stop my car
Data is raw data, a piece of data.
Information is a bit more elaborate on that piece of data.
Knowledge is where you have more background to that information and data and can piece things together a little more.
Wisdom is where you can take all three prior steps and put it all together to form something larger.
Explain what happens inside the Service Design and Service Transition phases of the ITIL Lifecycle. Short each paragraph for both, reference some of the processes or key activities as discussed in class / on the slides / in the book.
Preparing guiding and establishing the design for the services discussed in service strategy. Here is where you create a service design package which guides you through the development and requirements for the service being developed. Creating a structured design topology, creating plans, resources, policies, maintains standards and reports crucial for the service. It important to ensure you are bringing the business wants, as well as the utility and the warranty of the service. They look for ways to improve the service design process.
For approving the service to move to transition you must establish an acceptability requirements; that establish what the service needs to achieve in order to be deemed valuable and ready for deploy.
Then looking at all the service processes and the overall plan for the service.
Service transition is when you take all the information from service design and build, test, and implement the service. Ensuring all requirements are met to transition to service operations.
By testing out batches and ensuring they will be successful in the live environment. Ensuring documents are readily available to help support and guide the service transition. The Service Knowledge Management database holds crucial information pertaining to this stage. It helps show all the necessary documentation. The Configuration Management system hold the Configuration management databases and contains all relevant docs. The Configuration management database contains all the configuration items. Using levels, categories, and naming conventions (ensure to define them) to help organize all CI’s. It is important to create configurations linking the CI’s that relate together. And the services that are supported with all the documents, reports, incident requests, risk analysis etc.
Three types of Requests for Change were discussed in class. List each, and a summary of each of them including how they are different from each other.
Emergency change - A change that is requested in a sudden emergency, if something goes wrong and needs immediate attention. Usually needs one higher management member’s approval. Documentation can occur after the change has been processed. Ex- The computer lab images all fail so you request to revert them back to a previous image that worked
Normal Change - Has some level of risk, still needs approval before proceeding with the change. Documentation is recorded before / while rolling out the change. Ex- reimaging an entire lab with a new image that hasn’t been tested yet
Standard change - Something that is done more often and may not need approval anymore. Little to no risk. Ex- imaging a lab with a tried and true image that has been proven/tested for months with no issues
The ITIL term CAB stands for
change advisory board
The principles of Service Design talk about “the 4 P’s”. The first is People. What are the other 3 as discussed in the material? Just list.
people
process
product
partner
The ITIL term “SLA” refers to a Service
level agreement
What is involved/included in the Service Design Package?
Service design package involves ensuring that we can support the actual service that we are trying to create without having too much down time, including fault tolerance and the component failure analysis. The service design package also ensures that the parties involved have some sort of agreement between the two that they clearly know what is expected of the service provider.
What is involved/included in the Service Design Package?
Service design package involves ensuring that we can support the actual service that we are trying to create without having too much down time, including fault tolerance and the component failure analysis. The service design package also ensures that the parties involved have some sort of agreement between the two that they clearly know what is expected of the service provider.
What is the Service Catalog? What are CIs? How is the Service Catalog used in ITIL?
Service Catalog - A database that holds all of the live processes available, or processes ready for deployment. This makes the information available in one space.
Configuration items (CI) can be anything that needs to be configured/managed. Something physical like computers, something digital like software, or even a service.
The service catalog is used to keep track of different processes that are available, but keeping it all in one spot so it’s not hard to find.