Search
Topics
  Create an account Home  ·  Topics  ·  Downloads  ·  Your Account  ·  Submit News  ·  Top 10  
Modules
· Home
· Content
· FAQ
· Feedback
· Forums
· Search
· Statistics
· Surveys
· Top
· Topics
· Web Links
· Your_Account

Current Membership

Latest: EstoVef
New Today: 57
New Yesterday: 152
Overall: 130953

People Online:
Visitors: 63
Members: 6
Total: 69 .

Languages
Select Interface Language:


Major ITIL Portals
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

Related Resources
Service related resources
Service Level Agreement
Outsourcing

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 - Incident Management Setup Project Plan
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Incident Management Setup Project Plan

 
Post new topic   Reply to topic    ITIL Forum Index -> Related Topics
View previous topic :: View next topic  
Author Message
Ziad
Senior Itiler


Joined: Sep 27, 2006
Posts: 91

PostPosted: Thu Oct 19, 2006 8:07 am    Post subject: Incident Management Setup Project Plan Reply with quote

Dear All,
I am currently working on defining the project plan activities required to setup each and every one of the ITIL processes.
I started with the incident management and came up with the below list of activities to be executed in order.
Can you please let me know your comments and recommendations even if this means that totally different activities will be suggested?

- Check the current situation in terms of tools availability, staff level and their capability to execute the incident management activities.
- Launch an awareness campaign
- Request the required budget based on the analysis done in the first step.
- Purchase the tools (with implementation, customization/comfiguration, and support) along with the required hardware.
- Define the roles and responsibilities required to run the process.
- Define clear procedures and have them tested.
- Train the staff on the tools utilization and the procedures execution.

Thanks,
Z!
Back to top
View user's profile Send e-mail
Marcel
Senior Itiler


Joined: Sep 21, 2006
Posts: 63
Location: USA

PostPosted: Thu Oct 19, 2006 11:06 pm    Post subject: Reply with quote

After checking the current state (and for a part maybe combined with this activity), gather requirements for tools and processes.

Then, define your future state tool and process at a high level, by combining the generic ITIL processes with the local, more specific requirements that you have gathered. Also, get a management decision on whether or not customization of the standard tools that you are going to purchase will be allowed (preferrably not).

Perform a gap analysis to identify the gap between current state and future state in terms op process, tool, staffing, etc.

All this together is the analysis needed to get a solid foundation for your budget estimate for the implementation phase.

Another thing to consider: if your gap analysis shows a major gap between current and future state, you may want to see if you can implement your future state in steps instead of having a big bang scenario. Often, small changes can be made to the existing process that don't necessarily require big changes to the existing tools. For instance, make sure everybody uses the same severity levels and definitions. Or focus on keeping incident tickets up-to-date throughout their lifecycle (this is a change of behavior/culture).
Back to top
View user's profile
fighter
Senior Itiler


Joined: Mar 15, 2006
Posts: 68
Location: Thailand

PostPosted: Fri Oct 20, 2006 2:54 pm    Post subject: Reply with quote

Also include itil certification for your staff..

Listing out the services which IM is going to support may also help.

Cheers

Vimzie!
Back to top
View user's profile
m_croon
Senior Itiler


Joined: Aug 11, 2006
Posts: 262
Location: Netherlands

PostPosted: Sat Oct 21, 2006 4:01 am    Post subject: Reply with quote

Hi Z!

One (in y opinion vital) aspect I do not see in your list is reporting. Do not wait! Start right now. Define a simple (one page max.) report which lists # of incidents logged /closed / open per period (total organisation) and # of incidents open per team. Add a list of the top10 of oldest open incidents (a small table, one line per incident) and post this report weekly on a bulletin board, the door to the helpdesk room and in the back office. You will find that you'll get very different reactions from people Wink
However, it will help you get your control cycle in order (plan-do-check-act from mister deming) and it will support your awareness campaign.

Also, consider if you want to provide part of the report (the # of incdients logged / closed / open per period (total organisation) to inform your customer. This can give you necessary support frm your customer to implement incident management.
Back to top
View user's profile Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    ITIL Forum Index -> Related Topics All times are GMT + 10 Hours
Page 1 of 1

 
Jump to:  
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

Powered by phpBB 2.0.8 © 2001 phpBB Group
phpBB port v2.1 based on Tom Nitzschner's phpbb2.0.6 upgraded to phpBB 2.0.4 standalone was developed and tested by:
ArtificialIntel, ChatServ, mikem,
sixonetonoffun and Paul Laudanski (aka Zhen-Xjell).

Version 2.1 by Nuke Cops 2003 http://www.nukecops.com

Forums ©

 

Logos/trademarks property of respective owner. Comments property of poster. Rest 2004 Itil Community for Service Management & Foundation Certification. SV
Site source copyright (c)2003, and is Free Software under the GNU / GPL licence. All Rights Are Reserved.