Posted: Thu Oct 17, 2013 5:33 am Post subject: Prioritizing Problems - Resource Allocation
We are just starting off with Problem Management. To keep the process simple, we had intended to share our Incident prioritization matrix with Problem Management. (Imapct + Urgency). However it became quickly apprent that with 5 Problems of Priorty "1" it would be difficult to discerne which problem to address first. "FIFO" is not an option. How might we further define Problem priority? Some ideas we have had:
1) Number of related incidents
2) Affected system (some systems are more critical than others) but all can cause Priority 1 incidents.
3) Legal/Compliance impact.
If anyone else has struggled with this issue I would appreciate your feeback.
how many resources & time to dedicate to the analysis, etc of the problem
So a PRoblem - 1 - critical - System - Windows - would involve the majority of the time / resources to finding the underlying root cause - to include calls to Microsoft
while a problem 3 - irritating - system - windows - would involve one of the mid level engineers - Windows system - to investigate and may be involve technet etc and trying to replicate
Problem management unlike Incident managemetn is only concerned with the following
1 - find out the cause (unknown)
2 - determine how to resolve the cause once found
3 - choose the 'best' option
4 - test the solution while re-creating the problem(if possible)
5 - request change and deploy to production
6 .//wait// to see if the issue recurrs
From a long time kama'aina far from da kine _________________ John Hardesty
ITSM Manager's Certificate (Red Badge)
Change Management is POWER & CONTROL. /....evil laughter
Howzit John! Mahalo for your response. You are entirely correct. In fact, after some soul searching, I was able to come up with a priority tree that accounts for many of the items you have listed. Thank you for refocusing my thoughts.
I am too setting up problem management for my organization. I am concerned about how to manage the amount of raised problems.
How do you manage the length of time a problem is open? I mean a high impact issue, you need to have it fixed asap. Not to have small incremental steps which take months to complete.
And how do you deal with the smaller/minor issues, which get washed away by higher impacting problems, which do not have enough priority to work on. Do you close these after a certain time? Do you have guidelines/agreements for this in place?
The ITIL process flow does not have this option in place. It must be finished. Though, problem tickets which are open for more than 1 year does not hold any value in my opinion. What do you think?
Looking for a few perspectives on prioritization for problem management. Thanks in advance.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum