For general information and resources, ITIL and ITSM World is the most well known for both ITIL and ITIL Books. A shorter snapshot approach can be found at ITIL Zone
Note: ® ITIL is a registered trademark of OGC. This portal is totally independent and is in no way related to them. See our Feedback Page for more information.
The Itil Community Forum: Forums
ITIL :: View topic - Problem Coordinator reviewing incidents
Posted: Fri Jun 05, 2009 2:19 am Post subject: Problem Coordinator reviewing incidents
I know the answer is "it depends" but is there a good practice around the frequency an Incident Coordinator will reviewed Closed Incidents? Our group is just beginning to use Problem, they never used it before or used Change Request as a problem. So the number of problem tickets will more than likely be minimal at first. i'm just trying to set the expectation as many of the coordinators are functioning with multiple ITIL roles. Thx
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Fri Jun 05, 2009 5:52 pm Post subject:
dchell,
Best practice in this area is quite obvious.
The frequency is determined by the cost against benefit with an eye to risk. These are measures that can only be determined within an organization and must be governed by policy within that organization.
I have been able to say that without fully understanding your question.
- What is the purpose of this review?
- How does the number of problem tickets affect your need to review incidents?
- What do you mean by "used Change Request as a problem"?
- Are your Incident Co-ordinators being asked to perform a Problem Management role?
Assuming you are talking about pro-actively watching incidents to look for signs of problems, then I would have thought that you do it all the time.
If you are talking about reviewing incident management to ensure that there is consistency in things like categorization., hen I would think you review it something like every week if it is a new system and drop it to longer time periods as it beds in and matures.
I'd better stop this rambling because I'm still not quite sure what you are asking. Sorry. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
basically - I just want to know how often various Problem Coordinators check Closed Incidents to determine if they need to create a problem. That's all
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Sat Jun 06, 2009 3:26 am Post subject:
dchell wrote:
basically - I just want to know how often various Problem Coordinators check Closed Incidents to determine if they need to create a problem. That's all
[Sorry, I can't resist this.
You asked for best practice and now you want what people really do?
]
I would have thought best practice was to do it all the time. If you want to nip problems in the bud, you have to get at them while they are fresh. Why would you not look every day? - apart from you cannot afford the resource and you don't expect a useful return from the activity?
On the other hand, if all you are doing is trend analysis, then you need to step back a bit so that you do not confuse a glitch with a trend.
now as to the value of advice you get concerning what other people do:
If someone says they do it once a month and it's fine, don't forget to check that their services have very much the same characteristics as yours and that their customers have very similar priorities to yours.
The same goes for anyone who claims they do it daily, weekly, annually or any time they have a free moment. _________________ "Method goes far to prevent trouble in business: for it makes the task easy, hinders confusion, saves abundance of time, and instructs those that have business depending, both what to do and what to hope."
William Penn 1644-1718
Thanks I forgot that best practice is not what people do. haha
I'm recommending they check for the first month - every week and see how it goes from there. This is a new process for them - so want to be sure they are following it.
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
Forum FAQ
Search
Usergroups
Profile
Log in to check your private messages
Log in
I forgot that best practice is not what people do. haha
