ITIL: MANAGEMENT PRACTICES OVERVIEW Flashcards
is a set of organizational resources designed to perform work or accomplishing on objective
Practice
-supports multiple service value activities
-includes resources based on the 4 dimensions of service management
each practice
General Management Practices
Service Management Practices
Technical Management Practices
-used to be processes in ITIL v2 and v3
-now more general called practices
-use as plug-ins for activities in the value chain.
The ITIL 4 Practices
-have been adopted/adapted for service management from general business management domains
General Management Practices
-have been developed in service management and ITSM industries
Service Management Practices
-to maximize number of successful IT changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.
Change Control
is the addition, modification or removal of anything that could have a direct or indirect effect on services.
change
(change control)
-pre-authorized
- implement without additional authorization
standard
(change control)
-authorization on based on change type
-low-risk, someone who can make rapid decisions,
-very major, could be as highas management board
normal
(change control)
-expedited assessment and authorization
-may be separate change authority
emergency
(change control authorization)
-person or group who authorizes a change,
-assigned to a type of change to ensure efficient/effective change control.
-decentralized in high-velocity organizations (perr-review)
change authority
(change control authorization)
-used to help plan changes, assist in communication, avoid conflicts and assign resources.
change schedule
-to minimize negative impact of incidents by restoring normal service operation as quickly as possible
incident management
-is an unplanned interruption to a service or reduction in quality of a service
-may be escalated to a support team
incident
incidents should be
-logged
-managed to meet target resolution times
-prioritized
(problem management)
-incidents based on different impact
-major incidents
-information security incidents
design an incident practice for different types of incident
(incident management)
-based on agreed classification
-ensure hughes impact is resolved first
prioritize incidents
(incident management)
-link to configuration item, cnagesm problems, known errors, etc
-provide matching to other incidents, problems or known errors
use robust tool to log & manage incidents