Practices Flashcards

1
Q

a set of organizational resources designed for performing work or
accomplishing an objective.

A

A practice

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

Purpose of Practices

A

Each practice:
▪ Supports multiple service value chain activities
▪ Includes resources based on the 4 dimensions of service management

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

Types of Practices

A

o General management practices
o Service management practices
o Technical management practices

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

General Management Practices

A

General management practices have been adopted/adapted for service management
from general business management domains.

o There are 14 General Management Practices:
▪ ** Continual Improvement
▪ * Information Security Management
▪ * Relationship Management
▪ * Supplier Management
▪ Architecture Management
▪ Knowledge Management
▪ Measure and Reporting
▪ Portfolio Management
▪ Organizational Change Management
▪ Project Management
▪ Risk Management
▪ Service Financial Management
▪ Strategy Management
▪ Workforce and Talent Management
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

1st GMP. Continual Improvement

A

The purpose of the continual improvement practice is to align the organization’s
practices and services with changing business needs through the ongoing identification and improvement of services, service components, practices or any element involved in the efficient and effective management of products and services.

Key activities:
▪ Encouraging continual improvement across the organization
▪ Securing time and budget for continual improvement
▪ Identifying and logging improvement opportunities
▪ Assessing and prioritizing improvement opportunities
▪ Making business cases for improvement action
▪ Planning and implementing improvements
▪ Measuring and evaluating improvement results
▪ Coordinating improvement activities across the organization

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

is a database or structured document to track and manage improvement ideas from identification through to final action.

A

A continual improvement register (CIR)

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

2nd GMP. Information Security Management

A

The purpose of the information security management practice is to protect the
information needed by the organization to conduct its business.

o Includes understanding and managing risks to:
▪ Confidentiality
▪ Integrity
▪ Availability
▪ Authentication
▪ Non-repudiation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

3rd GMP. Relationship Management

A

The purpose of the relationship management practice is to establish and nurture the
links between the organization and its stakeholders at strategic and tactical levels.

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

4th GMP. Supplier Management

A

o The purpose of the supplier management practice is to ensure the organization’s
suppliers and their performance are managed appropriately to support the provision
of seamless, quality products, services and components.
o This can include creating closes, more collaborative relationships with key suppliers
to uncover and realize new value and reduce risk of failure.

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

Service Management Practices

A
o There are 17 SeviceManagement Practices:
▪ ** Change Control
▪ ** Incident Management
▪ ** Problem Management
▪ ** Service Desk
▪ ** Service Level Management
▪ ** Service Request Management
▪ * IT Asset Management
▪ * Monitoring and Event Management
▪ * Release Management
▪ * Service Configuration Management
▪ Service Continuity Management
▪ Availability Management
▪ Business Analysis
▪ Capacity and Performance Management
▪ Service Catalogue Management
▪ Service Design
▪ Service Validation and Testing
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Change Control

A

The purpose of the change control practice is to maximize the number of successful
IT changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.

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

The scope of change control

A

is defined by each organization. It will typically include all IT infrastructure, applications, documentation, processes, supplier relationships and anything else that might directly or indirectly impact a product or service.

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

he addition, modification, or removal of anything that could have a direct or indirect effect on IT services.

A

Change

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

Types of Change

A

▪ Standard
● Pre-authorized
● Implement without additional authorization

▪ Normal
● Authorization based on change type
● Low-risk, someone who can make rapid decisions
● Very major

▪ Emergency
● Expedited assessment and authority
● May be separate change authority

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

change authority

A

The person or group who authorizes a change is known as a change authority.

▪ In high velocity organizations, it is a common practice to decentralize change
approval, making the peer review a top predictor of high performance

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

change schedule

A

The change schedule is used to help plan changes, assist in communication, avoid
conflicts and assign resources.

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

Incident Management

A

The purpose of the incident management practice is to minimize the negative impact
of incidents by restoring normal service operation as quickly as possible.

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

an unplanned interruption to a service, or reduction in the

quality of service.

A

incident

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

Key notes of Incidents

A

● Incidents should be logged.
● Incidents should be managed to meet agreed target resolution times.
● Incidents should be prioritized.

Design the incident management practice appropriately for different types of incidents
▪ Incidents based on different impact
▪ Major incidents
▪ Information security incidents
o Prioritize incidents
▪ Based on agreed classification
▪ Ensure incidents with highest business impact are resolved first
o Use a robust tool to log and manage incidents
▪ Link to configuration items, changes, problems, known errors and other
knowledge
▪ Provide incident matching to other incidents, problems or known errors

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

swarming

A

This involves many different stakeholders working together initially, until it becomes very clear which of them is best placed to continue and which can move on to other tasks.
▪ Collaboration can facilitate information sharing and learning as well as helping to solve the incident more efficiently and effectively.

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

Problem Management

A

The purpose of the problem management practice is to reduce the likelihood and
impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.

22
Q

Problem

A

is a cause, or potential cause, of one or more incidents

23
Q

A known error

A

is a problem that has been analyzed and has not been

resolved.

24
Q

A workaround

A

is 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.
▪ Workarounds are documented in problem records
▪ Workarounds can be done at any stage, it doesn’t need to wait for analysis to
be complete
▪ If a workaround has been documented early in problem control, then this
should be reviewed and improved after problem analysis is complete

25
Q

Problem Management actions:

A
  1. Problem Identification
  2. Problem Control
  3. Error Control
26
Q

Problem Management interacts with:

A
▪ Incident management
▪ Risk management
▪ Change control
▪ Knowledge management
▪ Continual improvement
27
Q

Service Desk

A

The purpose of the service desk practice is to capture demand for incident resolution
and service requests. It should also be the entry point/single point of contact for the service provider with all of its users.

With increased automation and the gradual removal of technical debt, the focus of the service desk is to provide support for ‘people and business’ rather than simple technical issues.

28
Q

Service Desk Key notes

A

▪ Major influence on user experience and how the service provider is perceived by users
▪ Practical understanding of the wider organization – the empathetic link between the service provider and users
▪ The service desk can focus on excellent customer experience when personal contact is needed
▪ Support and development teams need to work in close collaboration with the service desk

29
Q
▪ Intelligent telephony systems
▪ Workflow systems
▪ Workforce management/resource planning systems
▪ Knowledge base
▪ Call recording and quality control
▪ Remote access tools
▪ Dashboard and monitoring tools
▪ Configuration management systems
A

Supporting technologies for a centralized service desk

30
Q

Virtual Service Desk

A

A virtual service desk allows agents to work from multiple, geographically-dispersed locations. It requires more sophisticated technology, allowing access from multiple locations and complex routing and escalation.

31
Q

Service Level Management

A

The purpose of the service level management practice is to set clear business-based
targets for service performance, so that the delivery of a service can be properly
assessed, monitored and managed against these targets.

32
Q

SLM KEY NOTES

A

Provides the end to end visibility of the organization’s services:
▪ Establishes a shared view of the services and target service levels with customers
▪ Collects, analyzes, stores and reports relevant metrics to ensure service levels are met
▪ Performs service reviews to ensure the current services continue to meet the organization and its customers’ needs
▪ Captures and reports on service issues including performance against defined service levels

33
Q

is a documented agreement between a service provider and a customer that identifies services required and the expected level of service.

SLA is a tool to measure the performance of services from the customer’s point of view.

A

A service level agreement (SLA)

34
Q

Key requirements for successful SLAs:

A

● Related to a defined service
● Should relate to defined outcomes, not just operational metrics
● Should reflect an agreement between the service provider and the
service consumer
● Must be simply written and easy to understand for all parties

35
Q

Service Level Management interacts with:

A
▪ Relationship management
▪ Business liaison
▪ Supplier management
▪ Skills and competencies
▪ Business analysis
36
Q

SLM Information sources:

A
▪ Customer engagement
● Initial listening
● Discovery and information capture
● Measurement and ongoing process discussions
● Asking simple open-ended questions

▪ Customer feedback
● Surveys
● Key business-related measures

▪ Operational metrics
▪ Business metrics

37
Q

Service Request Management

A

The purpose of the service request management practice is to support the agreed
quality of a service by handling all agreed user-initiated service requests in an
effective and user-friendly manner.

38
Q

Service Requests:

A

o Service requests are a normal part of service delivery, not a failure or degradation of service, which are handled as incidents.

o Service requests are pre-defined and pre-agreed and can usually be formalized with
clear, standard procedures.

39
Q

a request from a user or a user’s authorized representative that initiates a service action that has been agreed as a normal part of service delivery.

A

A Service Request

40
Q

Examples of Service Request

A

▪ Request for a service delivery action
▪ Request for information
▪ Request for provision of a resource or service ▪ Request access to a resource or service
▪ Feedback, compliments and complaints

41
Q

Service Requests key notes

A
  1. Service requests and their fulfilment should be standardized and automated to the greatest degree possible
  2. Opportunities for improvement should be identified and implemented to produce faster fulfilment times
  3. Policies should be established regarding what service requests will be fulfilled with limited or even no additional approvals
  4. The expectations of users regarding fulfilment times should be clearly set, based on what the organization can realistically deliver.
  5. Policies and workflows are needed to redirect service requests
  6. Some service requests require authorization according to financial, information security or other policies.
  7. Service requests may have simple workflows or quite complex workflows
  8. Some service requests can provide a self-service experience – completely fulfilled
    with automation
42
Q

IT Asset Management

A

The purpose of the IT asset management practice is to plan and manage the full lifecycle of all IT assets, to help the organization:
▪ Maximize value
▪ Control costs
▪ Manage risks
▪ Support decision-making about purchase, reuse and retirement of assets
▪ Meet regulatory and contractual requirements

o An IT asset is any valuable component that can contribute to delivery of an IT
product or service

43
Q

Monitoring and Event Management

A

The purpose of the monitoring and event management practice is to systematically
observe a service or service component, and record and report selected changes of
state identified as events.

This practice identifies and prioritizes infrastructure, services, business processes and
information security events, and establishes the appropriate response to those events,
including responding to conditions that could lead to potential faults or incidents.

44
Q
any change of state that has significance for the management of a
configuration item (CI) or IT service.
A

Event

45
Q

Release Management

A

The purpose of the release management practice is to make new and changed
services and features available for use.

46
Q

Service Configuration Management

A

to ensure that accurate
and reliable information about the configuration of services, and the Cis that support
them, is available when and where it is needed.

47
Q

any component that needs to be managed in order to

deliver an IT service.

A

A configuration item (CI)

48
Q

Technical Practices

Technical Management Practices

A

echnical management practices have been adapted from technology management
domains for service management purposes by expanding or shifting their focus from
technology solutions to IT services.

49
Q

Types of Technical Management Practices:

A

There are 3 Technical Management Practices:
▪ * Deployment Management
▪ Infrastructure and Platform Management
▪ Software Development and Management

50
Q

Deployment Management

A

The purpose of the deployment management practice is to move new or changed
hardware, software, documentation, processes, or any other component to live environments. It may also be involved in deploying components to other environments for testing or staging.