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 - Methodology For Incident Backlog
Posted: Fri Aug 06, 2010 12:21 pm Post subject: Methodology For Incident Backlog
Looking for any advice or systems that have worked for anyone in effectively tackling a large incident backlog. Some changes occurred recently that generated a significant amount of non-phone initiated incidents so they are just sitting there ticking away... I'm going to assign a dedicated team to them obviously reacting first to those that have breached (and furthest from) service level targets.
Joined: Mar 04, 2008 Posts: 1883 Location: Newcastle-under-Lyme
Posted: Fri Aug 06, 2010 7:14 pm Post subject: Re: Methodology For Incident Backlog
tmack wrote:
I'm going to assign a dedicated team to them obviously reacting first to those that have breached (and furthest from) service level targets.
It might be better, and your customer(s) might be happier, if you deal with the ones with greatest impact and risk to your customers first, rather than trying to protect your stats. _________________ "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
Joined: Oct 26, 2007 Posts: 295 Location: Calgary, Canada
Posted: Sat Aug 07, 2010 1:25 am Post subject:
I think the first order of business is to hire and ITIL consultant
But, like Diarmid, said, if resource augmentation is out of the question, tackle issues of highest importance. If possible, you can make it a primary task of selected (unlucky) few to clear the backlog. In my less fortunate days as a software developer, i used to work on issues dating back few years. It was fun contacting the customer with "Say, remember that problem you have 3 years ago. Well, i fixed it, so i want you to go and do a couple of tests on the system you no longer use to validate the resolution." I do have a point here - you may discover that some items in your backlog are not worth addressing.
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
