ITIL Deck Flashcards

(71 cards)

1
Q

The ITIL® 4 Foundation qualification is intended to?

A

Introduce candidates to the management of
modern IT-enabled services.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Key concepts of services and service management:
Service?

A

A means of enabling value co-creation by facilitating outcomes that customers want to
achieve, without the customer having to manage specific costs and risks.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Key concepts of services and service management:
Service management?

A

A set of specialized organizational capabilities for enabling value for
customers in the form of services.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Key concepts of services and service management:
Customer?

A

The role that defines the requirements for a service and takes responsibility for the
outcomes of service consumption.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Key concepts of services and service management:
User?

A

The role that uses services.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Key concepts of services and service management:
Sponsor?

A

The role that authorizes budget for service consumption.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Key concepts of services and service management:
Utility?

A

The functionality offered by a product or service to meet a particular need.
‘what the service does’
‘fit for purpose’

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Key concepts of services and service management:
Warranty?

A

Assurance that a product or service will meet agreed requirements.
‘how the service performs’
‘fit for use’

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Key concepts of creating value with services:
Value?

A

The perceived benefits, usefulness, and importance of something.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Key concepts of creating value with services:
Output?

A

A tangible or intangible deliverable of an activity.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Key concepts of creating value with services:
Outcome?

A

A result for a stakeholder enabled by one or more outputs.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Key concepts of creating value with services:
Cost?

A

The amount of money spent on a specific activity or resource.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Key concepts of creating value with services:
Risk?

A

A possible event that could cause harm or loss, or make it more difficult to achieve
objectives.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Key concepts of creating value with services:
Organization?

A

A person or a group of people that has its own functions with responsibilities,
authorities, and relationships to achieve its objectives.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Key concepts of service relationships:
Service offering?

A

A formal description of one or more services, designed to address the needs
of a target consumer group.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Key concepts of service relationships:
Service relationship management?

A

Joint activities performed by a service provider and a
service consumer to ensure continual value co-creation based on agreed and available service
offerings.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Key concepts of service relationships:
Service provision?

A

Activities performed by an organization to provide services. It includes
management of the provider’s resources, configured to deliver the service; ensuring access to
these resources for users; fulfillment of the agreed service actions; service level management;
and continual improvement. It may also include the supply of goods.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Key concepts of service relationships:
Service consumption?

A

Activities performed by an organization to consume services. It includes
the management of the consumer’s resources needed to use the service, service actions
performed by users, and the receiving (acquiring) of goods (if required).

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

The ITIL guiding principles:
Focus on value?

A

Everything that the organization does needs to map, directly or indirectly,
to value for the stakeholders.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

The ITIL guiding principles:
Start where you are?

A

Do not start from scratch and build something new without
considering what is already available to be leveraged.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

The ITIL guiding principles:
Progress iteratively with feedback?

A

Do not attempt to do everything at once. Even huge
initiatives must be accomplished iteratively. By organizing work into smaller, manageable
sections that can be executed and completed in a timely manner.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

The ITIL guiding principles:
Collaborate and promote visibility?

A

Working together across boundaries produces results
that have greater buy-in, more relevance to objectives, and increased likelihood of longterm
success.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

The ITIL guiding principles:
Think and work holistically?

A

No service, or element used to provide a service, stands
alone.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

The ITIL guiding principles:
Keep it simple and practical?

A

If a process, service, action, or metric fails to provide value or
produce a useful outcome, eliminate it. In a process or procedure, use the minimum number
of steps necessary to accomplish the objective(s). Always use outcome-based thinking to
produce practical solutions that deliver results.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
The ITIL guiding principles: Optimize and automate?
Eliminate anything that is truly wasteful and use technology to achieve whatever it is capable of.
26
The four dimensions of service management: Organizations and people?
This dimension ensures that the way an organization is structured and managed, as well as its roles, responsibilities, and systems of authority and communication, is well defined and supports its overall strategy and operating model.
27
The four dimensions of service management: Information and technology?
This dimension includes the information and knowledge used to deliver services, and the information and technologies used to manage all aspects of the service value system.
28
The four dimensions of service management: Partners and suppliers?
This dimension encompasses the relationships an organization has with other organizations that are involved in the design, development, deployment, delivery, support, and/or continual improvement of services.
29
The four dimensions of service management: Value streams and processes?
This dimension defines the activities, workflows, controls, and procedures needed to achieve the agreed objectives.
30
The ITIL service value system (SVS)
The ITIL SVS describes how all the components and activities of the organization work together as a system to enable value creation.
31
The ITIL service value system (SVS): Opportunity?
The possibility to add value for stakeholders or to improve the organization.
32
The ITIL service value system (SVS): Demand?
The need or desire for products and services from internal and external customers.
33
The ITIL service value system (SVS): Value?
The perceived benefits, usefulness and importance of something.
34
The ITIL service value system (SVS): Guiding principles?
Recommendations that guide an organization in all circumstances, regardless of changes in its goals, strategies, type of work, or management structure.
35
The ITIL service value system (SVS): Governance?
The means by which an organization is directed and controlled.
36
The ITIL service value system (SVS): Service value chain?
A set of interconnected activities that an organization performs to deliver a valuable product or service to its consumers and to facilitate value realization.
37
The ITIL service value system (SVS): Practices?
Sets of organizational resources designed for performing work or accomplishing an objective.
38
The ITIL service value system (SVS): Continual improvement
A recurring organizational activity performed at all levels to ensure that an organization’s performance continually meets stakeholders’ expectations.
39
The service value chain (SVC) and value chain activities: Plan?
The purpose of the plan value chain activity is to ensure a shared understanding of the vision, current status, and improvement direction for all four dimensions and all products and services across an organization.
40
The service value chain (SVC) and value chain activities: Improve?
The purpose of the improve value chain activity is to ensure continual improvement of products, services, and practices across all value chain activities and the four dimensions of service management.
41
The service value chain (SVC) and value chain activities: Engage?
The purpose of the engage value chain activity is to provide a good understanding of stakeholder needs, transparency, continual engagement, and good relationships with all stakeholders.
42
The service value chain (SVC) and value chain activities: Design & transition?
The purpose of the design & transition value chain activity is to ensure products and services continually meet stakeholder expectations for quality, costs, and time to market.
43
The service value chain (SVC) and value chain activities: Obtain/build?
The purpose of the obtain/build value chain activity is to ensure that service components are available when and where they are needed, and that they meet agreed specifications.
44
The service value chain (SVC) and value chain activities: Deliver & support?
The purpose of the deliver and support value chain activity is to ensure that services are delivered and supported according to agreed specifications and stakeholder’s expectations.
45
ITIL practice
1. Information security management. 2. Relationship management. 3. Supplier management. 4. IT asset management. 5. Monitoring and event management. 6. Release management. 7. Service configuration management. 8. Deployment management. 9. Continual improvement. 10. Change enablement. 11. Incident management. 12. Problem management. 13. Service request management. 14. Service desk. 15.Service level Management
46
Information security management
The purpose of this practice is to protect the information needed by the organization to conduct its business.
47
Security objectives include:
*Confidentiality: A security objective that ensures information is not made available or disclosed to unauthorized entities. * Integrity: A security objective that ensures information is only modified by authorized personnel and activities. * Availability: A security objective that ensures information is always accessible to authorized personnel whenever required. *Non-repudiation (ensuring that someone can’t deny that they took an action).
48
Relationship management
The purpose of this practice is to establish and nurture the links between the organization and its stakeholders at strategic and tactical levels. It includes the identification, analysis, monitoring, and continual improvement of relationships with and between stakeholders.
49
Supplier management
The purpose of this practice is to ensure that the organization’s suppliers and their performances are managed appropriately to support the seamless provision of quality products and services.
50
Supplier management: Sourcing:
The activity of planning and obtaining resources from a particular source type, which could be internal or external, centralized or distributed, and open or proprietary.
51
IT asset management
The purpose of this practice is to plan and manage the full life cycle of all IT assets, to help the organization maximize value; control costs; manage risks; support decision-making about purchase, re-use, and retirement of assets; and meet regulatory and contractual requirements.
52
IT asset management: IT asset?
Any financially valuable component that can contribute to the delivery of an IT product or service.
53
Monitoring and event management:
The purpose of this practice is to systematically observe services and service components, and record and report selected changes of state identified as events.
54
Monitoring and event management: Monitoring:
The repeated observation of a system, practice, process, service, or other entity to detect events and ensure that the current status is known.
55
Monitoring and event management: Event:
Any change of state that has significance for the management of a service or other configuration item.
56
Monitoring and event management: Event: The three event types are:
i. Informational events, which do not require action at the time they are identified, but analysing the data gathered from them at a later date may uncover desirable, proactive steps that can be beneficial to the service. ii. Warning events, which allow action to be taken before any negative impact is actually experienced by the business. iii. Exception events, which indicate that a breach to an established norm has been identified, and require action, even though business impact may not yet have been experienced.
57
Monitoring and event management: Event management:
Recording and managing those monitored changes of state that are defined by the organization as an event, determining their significance, and identifying and initiating the correct control action to manage them.
58
Release management:
The purpose of this practice is to make new and changed services and features available for use.
59
Service configuration management:
The purpose of this practice is to ensure that accurate and reliable information about the configuration of services, and the configuration items (CIs) that support them, is available when and where it is needed. Configuration item (CI): Any component that needs to be managed in order to deliver an IT service.
60
Deployment management:
The purpose of this practice is to move new or changed hardware, software, documentation, processes, or any other component to live environments
61
Continual improvement:
The purpose of this practice is to align the organization’s practices and services with changing business needs through the ongoing improvement of products, services, and practices, or any element involved in the management of products and services.
62
The continual improvement model:
A structured approach to implementing improvements. Use of the model increases the likelihood that ITSM initiatives will be successful, puts a strong focus on customer value, and ensures that improvement efforts can be linked back to the organization’s vision.
63
Continual improvement register (CIR):
Database or structured document to track and manage improvement ideas from identification through to final action
64
Change enablement:
The purpose of this practice is to maximize the number of successful service and product changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.
65
Change enablement: Key terms include:
* Change: The addition, modification, or removal of anything that could have a direct or indirect effect on services. * Request for change (RFC): A description of a proposed change used to initiate change enablement. * Change authority: A person or group responsible for authorizing a change. * Standard change: A low-risk, pre-authorized change that is well understood and fully documented, and which can be implemented without needing additional authorization. * Normal change: A change that must be scheduled, assessed, and authorized following a process. * Emergency change: A change that must be introduced as soon as possible. * Change schedule: A calendar that shows planned and historical changes. * Change model: A repeatable approach to the management of a particular type of change. * Post-implementation review (PIR): A review after the implementation of a change, to evaluate success and identify opportunities for improvement
66
Incident management
The purpose of this practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible.
67
Incident management: Key terms include:
* Incident: An unplanned interruption to a service or reduction in the quality of a service. * Major incident: An incident with significant business impact, requiring an immediate coordinated resolution. * Swarming: A technique to help manage incidents, which involves many different stakeholders working together initially, until it becomes clear which of them is best placed to continue and which can move on to other tasks.
68
Problem management
The purpose of this practice is to reduce the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors. * Problem: A cause, or potential cause, of one or more incidents. * Known error: A problem that has been analyzed but has not been resolved. * Workaround: A solution that reduces or eliminates the impact of an incident or problem for which a full resolution is not yet available. Some workarounds reduce the likelihood of incidents. * Problem identification: Activities that identify and log problems. These include performing trend analysis of incident records; detection of duplicate and recurring issues by users, service desk, and technical support staff; during major incident management, identifying a risk that an incident could recur; analysing information received from suppliers and partners; and analysing information received from internal software developers, test teams, and project teams. * Problem control: Problem control activities include problem analysis, and documenting workarounds and known errors. * Error control: manage known errors, which are problems where initial analysis has been completed; it usually means that faulty components have been identified. Error control also includes identification of potential permanent solutions which may result in a change request for implementation of a solution, but only if this can be justified in terms of cost, risks, and benefits.
69
Service request management
The purpose of this practice is to support the agreed quality of a service by handling all pre-defined, user-initiated service requests in an effective and user-friendly manner. * Service request: A request from a user or a user’s authorized representative that initiates a service action which has been agreed as a normal part of service delivery.
70
Service desk
The purpose of this practice is to capture demand for incident resolution and service requests. It should also be the entry point and single point of contact for the service provider with all of its users. Escalation: The act of sharing awareness or transferring ownership of an issue or work item.
71
Service level management
The purpose of this practice is to set clear business-based targets for service levels, and to ensure that delivery of services is properly assessed, monitored, and managed against these targets. Service level: One or more metrics that define expected or achieved service quality. Metric: A measurement or calculation that is monitored or reported for management and improvement. Service level agreement (SLA): A documented agreement between a service provider and a customer that identifies both services required and the expected level of service. * Watermelon effect: Like a watermelon the SLA may appear green on the outside but is actually red inside. For instance, a system may have been unavailable for an amount of time that is acceptable according to the SLA, but if the unavailability occurred when there was an important process happening, customer/user satisfaction will be low, even though the SLA was met.