Difference between revisions of "ITIL practices"

From CNM Wiki
Jump to: navigation, search
(Created page with " Continual Improvement ● The purpose of the continual improvement practice is to align the organization's practices ang services with changing business needs through the on...")
 
(→‎Everyone-involved practice)
 
(71 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
Continual Improvement
+
The [[ITIL practices]] are those [[practice]]s that the [[ITIL]] framework recognizes as ''practices''. The ''ITIL'' definitions may differ from the others. According to the [[ITIL Foundation 4e by Axelos]],<blockquote>A practice is a set of organizational resources designed for performing work or accomplishing an objective.</blockquote>
−
● The purpose of the continual improvement practice is to align the organization's practices ang 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.
+
In the [[ITIL]] universe, each practice supports multiple activities of the [[ITIL service value chain]] and includes resources based on the [[four dimensions of service management]].
−
+
 
−
Categories of Practices
+
 
−
● What is Practice?
+
==Trivia==
−
o A practice is a set of organizational resources designed for performing work or accomplishing an objective.
+
===Everyone-involved-in practice===
−
o Each practice:
+
:According to the [[service value system]] developed by [[AXELOS Limited]], everyone should be involved in the [[continual improvement practice]]. Because of that, this practice caps not only the ''general management practices'' it belongs to, but also all the other practices.
−
▪ Supports multiple service value chain activities
+
 
−
▪ Includes resources based on the 4 dimensions of service management
+
===Categories===
−
● Introduction to the ITIL Practices
+
:*[[#General Management Practices|General Management Practices]], which are adopted/adapted for service management from general business.
−
o General management practices
+
:*[[#Service Management Practices|Service Management Practices]], which are specific to [[service management]] and [[ITSM]].
−
o Service management practices
+
:*[[#Technical Management Practices|Technical Management Practices]], which are adopted/adapted for service management from technology management.
−
o Technical management practices
+
 
−
+
==General Management Practices==
−
General Management Practices
+
General management practices have been adopted/adapted for service management from general business management domains.
−
● General Management Practices
+
 
−
o General management practices have been adopted/adapted for service management from general business management domains.
+
===15 practices===
−
o There are 15 General Management Practices:
+
:There are 15 general management practices:
−
▪ ** Continual Improvement
+
:#'''To understand''' according to [[Bloom's taxonomy]] for the [[ITIL 4 Foundation]] exam:
−
▪ * Information Security Management
+
:#*[[Continual improvement practice]]
−
▪ * Relationship Management
+
:#'''To recall''' according to [[Bloom's taxonomy]] for the [[ITIL 4 Foundation]] exam:
−
▪ * Supplier Management
+
:#*[[Information security management practice]].
−
▪ Architecture Management
+
:#*[[Relationship management practice]].
−
▪ Knowledge Management
+
:#*[[Supplier management practice]].
−
▪ Measure and Reporting
+
:#'''Not covered''' by the [[ITIL 4 Foundation]] exam:
−
▪ Portfolio Management
+
:#*[[Architecture management practice]].
−
▪ Organizational Change Management
+
:#*[[Knowledge management practice]].
−
▪ Project Management
+
:#*[[Measurement and reporting]].  
−
▪ Risk Management
+
:#*[[Portfolio management practice]].
−
▪ Service Financial Management
+
:#*[[Organizational change management practice]].
−
▪ Strategy Management
+
:#*[[Project management practice]].
−
▪ Workforce and Talent Management
+
:#*[[Risk management practice]].
−
o Practices with (**) must be known in-depth for the exam
+
:#*[[Service financial management practice]].
−
o Practices with (*) are recall only
+
:#*[[Strategy management practice]].
−
o Practices without a (**) or (*) are not covered by the exam
+
:#*[[Workforce and talent management practice]].
−
● ** Continual Improvement
+
 
−
o The purpose of the continual improvement practice is to align the organization's practices ang 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.
+
===Continual Improvement===
−
o Key activities:
+
:''Main wikipage: [[Continual improvement practice]]
−
▪ Encouraging continual improvement across the organization
+
 
−
▪ Securing time and budget for continual improvement
+
: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.
−
▪ Identifying and logging improvement opportunities
+
 
−
▪ Assessing and prioritizing improvement opportunities
+
===Information Security Management===
−
▪ Making business cases for improvement action
+
:''Main wikipage: [[Information security management practice]]''
−
▪ Planning and implementing improvements
+
 
−
▪ Measuring and evaluating improvement results
+
:The purpose of the [[information security management practice]] is to protect the information needed by the organization to conduct its business.
−
▪ Coordinating improvement activities across the organization
+
 
−
+
===Relationship Management===
−
o A continual improvement register (CIR) is a database or structured document to track and manage improvement ideas from identification through to final action.
+
:''Main wikipage: [[Relationship management practice]]''
−
+
 
−
● * Information Security Management
+
: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.
−
o 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:
+
===Supplier Management===
−
▪ Confidentiality
+
:''Main wikipage: [[Supplier management practice]]''
−
▪ Integrity
+
 
−
▪ Availability
+
: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.
−
▪ Authentication
+
 
−
▪ Non-repudiation
+
==Service Management Practices==
−
● * Relationship Management
+
Service management practices have been developed in service management and [[IT service management]] ([[ITSM]]) industries.
−
o 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.
+
 
−
+
===17 practices===
−
● * Supplier Management
+
:There are 17 service management practices:
−
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.
+
:#'''To understand''' according to [[Bloom's taxonomy]] for the [[ITIL 4 Foundation]] exam:
−
o This can include creating closes, more collaborative relationships with key suppliers to uncover and realize new value and reduce risk of failure.
+
:#*[[Change control practice]].
−
+
:#*[[Incident management]].
−
Service Management Practices
+
:#*[[Problem management practice]].
−
● Service Management Practices
+
:#*[[Service desk]].
−
o Service management practices have been developed in service management and IT service management (ITSM) industries.
+
:#*[[Service level management practice]].
−
o There are 17 General Management Practices:
+
:#*[[Service request management practice]].
−
▪ ** Change Control
+
:#'''To recall''' according to [[Bloom's taxonomy]] for the [[ITIL 4 Foundation]] exam:
−
▪ ** Incident Management
+
:#*[[IT asset management practice]].
−
▪ ** Problem Management
+
:#*[[Monitoring and event management practice]].
−
▪ ** Service Desk
+
:#*[[Release management practice]].
−
▪ ** Service Level Management
+
:#*[[Service configuration management practice]].
−
▪ ** Service Request Management
+
:#*[[Service continuity management practice]].
−
▪ * IT Asset Management
+
:#'''Not covered''' by the [[ITIL 4 Foundation]] exam:
−
▪ * Monitoring and Event Management
+
:#*[[Availability management practice]].  
−
▪ * Release Management
+
:#*[[Business analysis practice]].
−
▪ * Service Configuration Management
+
:#*[[Capacity and performance management practice]].  
−
▪ * Service Continuity Management
+
:#*[[Service catalogue management practice]].
−
▪ Availability Management
+
:#*[[Service design practice]].  
−
▪ Business Analysis
+
:#*[[Service validation and testing practice]].
−
▪ Capacity and Performance Management
+
 
−
▪ Service Catalogue Management
+
===Change Control===
−
▪ Service Design
+
:''Main wikipage: [[Change control practice]]''
−
▪ Service Validation and Testing
+
 
−
o Practices with (**) must be known in-depth for the exam
+
:A [[change]] is the addition, modification, or removal of anything that could have a direct or indirect effect on IT services. 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.
−
o Practices with (*) are recall only
+
 
−
o Practices without a (**) or (*) are not covered by the exam
+
===Incident Management===
−
  ● Change Control
+
:''Main wikipage: [[Incident management]]''
−
o 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.
+
 
−
+
:An [[incident]] is an unplanned interruption to a service, or reduction in the quality of service. The purpose of the [[incident management]] is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible.
−
o The scope of change control 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.
+
 
−
o A change is the addition, modification, or removal of anything that could have a direct or indirect effect on IT services.
+
===Problem Management===
−
▪ Standard
+
:''Main wikipage: [[Problem management practice]]''
−
● Pre-authorized
+
 
−
● Implement without additional authorization
+
:A [[problem]] is a cause, or potential cause, of one or more [[incident]]s. 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.
−
▪ Normal
+
 
−
● Authorization based on change type
+
===Service Desk===
−
● Low-risk, someone who can make rapid decisions
+
:''Main wikipage: [[Service desk]]''
−
● Very major
+
 
−
▪ Emergency
+
: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.
−
● Expedited assessment and authority
+
 
−
● May be separate change authority
+
===Service Level Management===
−
o The person or group who authorizes a change is known as a change authority.
+
:''Main wikipage: [[Service level management practice]]''
−
▪ In high velocity organizations, it is a common practice to decentralize change approval, making the peer review a top predictor of high performance
+
 
−
o The change schedule is used to help plan changes, assist in communication, avoid conflicts and assign resources.
+
: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.
−
● Incident Management
+
 
−
o The purpose of the incident management practice is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible.
+
===Service Request Management===
−
▪ An incident is an unplanned interruption to a service, or reduction in the quality of service.
+
:''Main wikipage: [[Service request management practice]]''
−
+
 
−
● Incidents should be logged.
+
:A [[service request]] is 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. 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.
−
● Incidents should be managed to meet agreed target resolution times.
+
 
−
● Incidents should be prioritized.
+
===IT Asset Management===
−
o Design the incident management practice appropriately for different types of incidents
+
:''Main wikipage: [[IT asset management practice]]''
−
▪ Incidents based on different impact
+
 
−
▪ Major incidents
+
:An [[IT asset]] is any valuable component that can contribute to delivery of an IT product or service. The purpose of the IT asset management practice is to plan and manage the full lifecycle of all IT assets, to help the organization.
−
▪ Information security incidents
+
 
−
o Prioritize incidents
+
===Monitoring and Event Management===
−
▪ Based on agreed classification
+
:''Main wikipage: [[Monitoring and event management practice]]''
−
▪ Ensure incidents with highest business impact are resolved first
+
 
−
o Use a robust tool to log and manage incidents
+
:An [[event]] is any change of state that has significance for the management of a [[configuration item]] ([[CI]]) or IT service. 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.
−
▪ Link to configuration items, changes, problems, known errors and other knowledge
+
 
−
▪ Provide incident matching to other incidents, problems or known errors
+
===Release Management===
−
o Incidents may be escalated to a support team for resolution. The routing is typically based on the incident category. Anyone working on an incident should provide quality, timely updates. Incident management requires a high level of collaboration within and between teams.
+
:''Main wikipage: [[Release  management practice]]''
−
o Some organizations use a technique called swarming to help manage incidents. 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.
+
:The purpose of the release management practice is to make new and changed services and features available for use.
−
+
 
−
● Problem Management
+
===Service Configuration Management===
−
o 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.
+
:''Main wikipage: [[Service configuration management practice]]''
−
▪ A problem is a cause, or potential cause, of one or more incidents
+
 
−
▪ A known error is a problem that has been analyzed and has not been resolved.
+
:A [[configuration item]] ([[CI]]) is any component that needs to be managed in order to deliver an IT service. The purpose of service configuration management practice is 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.
−
o A workaround 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
+
===Service Continuity Management===
−
▪ Workarounds can be done at any stage, it doesn't need to wait for analysis to be complete
+
:''Main wikipage: [[Service continuity management practice]].
−
▪ If a workaround has been documented early in problem control, then this should be reviewed and improved after problem analysis is complete
+
 
−
o Problem Management interacts with:
+
==Technical Management Practices==
−
▪ Incident management
+
Technical 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.
−
▪ Risk management
+
 
−
▪ Change control
+
===3 practices===
−
▪ Knowledge management
+
:There are 3 technical management practices:
−
▪ Continual improvement
+
:#'''To recall''' according to [[Bloom's taxonomy]] for the [[ITIL 4 Foundation]] exam:
−
+
:#*[[Deployment management practice]].
−
● Service Desk
+
:#'''Not covered''' by the [[ITIL 4 Foundation]] exam:
−
o 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.
+
:#*[[Infrastructure and platform management practice]].
−
o 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.
+
:#*[[Software development and management practice]].
−
▪ 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
+
===Deployment Management===
−
▪ The service desk can focus on excellent customer experience when personal contact is needed
+
:''Main wikipage: [[Deployment management practice]]''
−
▪ Support and development teams need to work in close collaboration with the service desk
+
 
−
+
: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.
−
o Supporting technologies for a centralized service desk
 
−
▪ 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
 
−
o 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.
 
−
o The service desk may not need to be highly technical, although some are.
 
−
 
−
● Service Level Management
 
−
o 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.
 
−
o 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
 
−
o A service level agreement (SLA) 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.
 
−
▪ Key requirements for successful SLAs:
 
−
● 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
 
−
o Interacts with:
 
−
▪ Relationship management
 
−
▪ Business liaison
 
−
▪ Supplier management
 
−
 
−
▪ Business analysis
 
−
▪ Skills and competencies
 
−
o Information Sources:
 
−
▪ 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
 
−
• Service Request Management
 
−
o 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.
 
−
o Service requests are pre-defined and pre-agreed and can usually be formalized with clear, standard procedures.
 
−
 
−
o Service requests are a normal part of service delivery, not a failure or degradation of service, which are handled as incidents.
 
−
o A service request is 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.
 
−
§ Fulfilment of service requests may include changes to services or their components; usually these are standard changes.
 
−
o Some examples of a service request:
 
−
§ 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
 
−
o Service requests and their fulfilment should be standardized and automated to the greatest degree possible,
 
−
o Opportunities for improvement should be identified and implemented to produce faster fulfilment times and take additional advantage of automation.
 
−
o Policies should be established regarding what service requests will be fulfilled with limited or even no additional approvals so that fulfilment can be streamlined.
 
−
o The expectations of users regarding fulfilment times should be clearly set, based on what the organization can realistically deliver.
 
−
o Policies and workflows are needed to redirect service requests that should actually be managed as incidents or changes.
 
−
o Some service requests require authorization according to financial, information security or other policies.
 
−
o Service request management depends on well-designed processes and procedures, which are operationalized through tracking and automation tools.
 
−
o Service requests may have simple workflows or quite complex workflows
 
−
o Steps to fulfill requests should be well-known and proven
 
−
o The service provider can agree to fulfillment times and provide clear status communication to users
 
−
o Some service requests can provide a self-service experience – completely fulfilled with automation
 
−
o Leverage existing workflow models whenever possible to improve efficiency and maintainability.
 
−
 
−
● IT Asset Management
 
−
o 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
 
−
● Monitoring and Event Management
 
−
o 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.
 
−
o 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.
 
−
o An event is any change of state that has significance for the management of a configuration item (CI) or IT service.
 
−
● Release Management
 
−
o The purpose of the release management practice is to make new and changed services and features available for use.
 
−
 
−
● Service Configuration Management
 
−
o The purpose of service configuration management practice is 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.
 
−
o A configuration item (CI) is any component that needs to be managed in order to deliver an IT service.
 
−
 
−
Technical Practices
 
−
● Technical Management Practices
 
−
o Technical 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.
 
−
o There are 3 Technical Management Practices:
 
−
▪ * Deployment Management
 
−
▪ Infrastructure and Platform Management
 
−
▪ Software Development and Management
 
−
o Practices with (*) is recall only
 
−
o Practices without a (*) is not covered by the exam
 
−
● Deployment Management
 
−
o 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.
 

Latest revision as of 18:42, 30 December 2020

The ITIL practices are those practices that the ITIL framework recognizes as practices. The ITIL definitions may differ from the others. According to the ITIL Foundation 4e by Axelos,

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

In the ITIL universe, each practice supports multiple activities of the ITIL service value chain and includes resources based on the four dimensions of service management.


Trivia

Everyone-involved-in practice

According to the service value system developed by AXELOS Limited, everyone should be involved in the continual improvement practice. Because of that, this practice caps not only the general management practices it belongs to, but also all the other practices.

Categories

General Management Practices

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

15 practices

There are 15 general management practices:
  1. To understand according to Bloom's taxonomy for the ITIL 4 Foundation exam:
  2. To recall according to Bloom's taxonomy for the ITIL 4 Foundation exam:
  3. Not covered by the ITIL 4 Foundation exam:

Continual Improvement

Main wikipage: Continual improvement practice
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.

Information Security Management

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

Relationship Management

Main wikipage: Relationship management practice
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.

Supplier Management

Main wikipage: Supplier management practice
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.

Service Management Practices

Service management practices have been developed in service management and IT service management (ITSM) industries.

17 practices

There are 17 service management practices:
  1. To understand according to Bloom's taxonomy for the ITIL 4 Foundation exam:
  2. To recall according to Bloom's taxonomy for the ITIL 4 Foundation exam:
  3. Not covered by the ITIL 4 Foundation exam:

Change Control

Main wikipage: Change control practice
A change is the addition, modification, or removal of anything that could have a direct or indirect effect on IT services. 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.

Incident Management

Main wikipage: Incident management
An incident is an unplanned interruption to a service, or reduction in the quality of service. The purpose of the incident management is to minimize the negative impact of incidents by restoring normal service operation as quickly as possible.

Problem Management

Main wikipage: Problem management practice
A problem is a cause, or potential cause, of one or more incidents. 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.

Service Desk

Main wikipage: Service desk
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.

Service Level Management

Main wikipage: Service level management practice
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.

Service Request Management

Main wikipage: Service request management practice
A service request is 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. 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.

IT Asset Management

Main wikipage: IT asset management practice
An IT asset is any valuable component that can contribute to delivery of an IT product or service. The purpose of the IT asset management practice is to plan and manage the full lifecycle of all IT assets, to help the organization.

Monitoring and Event Management

Main wikipage: Monitoring and event management practice
An event is any change of state that has significance for the management of a configuration item (CI) or IT service. 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.

Release Management

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

Service Configuration Management

Main wikipage: Service configuration management practice
A configuration item (CI) is any component that needs to be managed in order to deliver an IT service. The purpose of service configuration management practice is 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.

Service Continuity Management

Main wikipage: Service continuity management practice.

Technical Management Practices

Technical 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.

3 practices

There are 3 technical management practices:
  1. To recall according to Bloom's taxonomy for the ITIL 4 Foundation exam:
  2. Not covered by the ITIL 4 Foundation exam:

Deployment Management

Main wikipage: Deployment management practice
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.
Retrieved from "https://pravka.bskol.com/w/index.php?title=ITIL_practices&oldid=70291"