Prioritizing Incidents with the Same Priority

March 29th, 2014 | Posted by Don Boylan in Incident Management
Q:

I’m starting to bring ITIL process into being in our organization, however I have this issue with Incident priorities. I currently have 5 priorities “Critical through to Query” but still end up in the same position that I have 50 Incidents all with the priority of “Standard” – this is the correct priority based on Impact x Urgency, but the question is how do you then sub define those 50 to see which Incident gets completed next. We range from arguments of “first come first served” which does not take into account Business Need, all the way through to “the Analyst should use their judgment” which means cherry picking.

A:

One aspect of an Incident that needs to be considered when attacking a large number of Incidents with the same Priority is Expected Effort. Obviously, good judgment needs to be used, but attacking them in order of least effort to most effort will allow for many more Incidents to be resolved.

Keep in mind that following this rule of thumb too far will lead you down a path where you exceed your SLA on all the highest effort Incidents. Something you probably want to avoid.

You can follow any responses to this entry through the RSS 2.0 You can leave a response, or trackback.

Leave a Reply

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