Main Menu
Home / IT Governance / Legacy Support / Planning for Major Incidents

Planning for Major Incidents

In this post by Simon Morris, the particulars and best practices around planning and dealing with major incidents in the ITSM/ITIL mindset. By first defining a major incident as an incident affecting more than one business unit, user, a certain type of device, or a complete lack of service (rather than degradation), Morris better frames the important steps that come while dealing with a major incident. As is typical with any well-established process, a key factor comes in recording the proper metrics to avoid repeated errors, and to strengthen the optimization of the team.



About Anne Grybowski

Anne is a former staff writer for CAI's Accelerating IT Success, with a degree in Media Studies from Penn State University.

Check Also

COBOL Is Still Around Because Nothing Better Has Replaced It

When COBOL was made in 1959, no one could have dreamed that it would outlive …

Leave a Reply

Your email address will not be published. Required fields are marked *

Sorry, but this content
is for our subscribers only!

But subscribing to ACCELERATING IT SUCCESS is FREE and only one click away!
Join more than 40,000 IT Professionals and get the best IT management articles to your mailbox with Accelerating IT Success!

Unsubscribe at any time