Exin Updated ITIL Exam Questions and Answers by emile

Effective incident management often requires a high level of collaboration within and between teams as this can facilitate information-sharing and learning, as well as helping to solve the incident more efficiently and effectively. There may also be a need for good collaboration tools so that people working on an incident can work together effectively. One technique that takes advantage of collaboration is termed swarming. This brings many different stakeholders together to work on the issue. Management of incidents may require frequent interaction with third party suppliers, and routine management of this aspect of supplier contracts is often part of the incident management practice.

https://www.bmc.com/blogs/itil-incident-management/

No service, practice, process, department, or supplier stands alone. The outputs that the organization delivers to itself, its customers, and other stakeholders will suffer unless it works in an integrated way to handle its activities as a whole, rather than as separate parts.

Taking a holistic approach to service management includes establishing an understanding of how all the parts of an organization work together in an integrated way (remember the four dimensions of service management?), including having an end-to-end visibility of how demand is captured and translated into outcomes. In a complex system, the alteration of one element can impact others and, where possible, these impacts need to be identified, analysed and planned for.

To apply this principle successfully, consider this advice:

• Recognize the complexity of the systems
• Collaboration is key to thinking and working holistically
• Where possible, look for patterns in the needs of and interactions between system elements
• Automation can facilitate working holistically

https://www.bmc.com/blogs/itil-guiding-principles/

• Emergency changes. These are changes that must be implemented as soon as possible; for example, to resolve an incident or implement a security patch. Emergency changes are not typically included in a change schedule, and the process for assessment and authorization is expedited to ensure they can be implemented quickly. As far as possible, emergency changes should be subject to the same testing, assessment, and authorization as normal changes, but it may be acceptable to defer some documentation until after the change has been implemented, and sometimes it will be necessary to implement the change with less testing due to time constraints. There may also be a separate change authority for emergency changes, typically including a small number of senior managers who understand the business risks involved.”

https://itsm.tools/why-what-change-management/#:~:text=Emergency%20changes. &text=Emergency%20changes%20are%20not%20typically,they%20can%20be%20implemented%20quickly.