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: M9230
New Today: 55
New Yesterday: 87
Overall: 139321

People Online:
Visitors: 51
Members: 0
Total: 51

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 - ITIL & long project development
 Forum FAQForum FAQ   SearchSearch   UsergroupsUsergroups   ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

ITIL & long project development

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


Joined: Mar 14, 2008
Posts: 32
Location: Porto, PO.

PostPosted: Wed Apr 09, 2008 10:07 pm    Post subject: ITIL & long project development Reply with quote

Hi.
I’d like to include in my ITIL implementation all user’s requests for internal development of small/big software modules (e.g. SQL script to generate a specific report, a full web application for the intranet, etc).

Let’s say that there is a report that needs to be provided to an external entity by our accounting dept.
In a simplistic view, I would start by entering an incident such as “Unable to provide report to external entity”, then pass it on to PM which would provide the requirement analysis procedure that would take place so that requirements of the module can be defined.

Development could take several days or weeks (leaving the incident unsolved for a long time), then Change & Config. would take place and once the script would become available, tested, approved and go to production, the incident would be closed.

My post is about to get to know other's experience/opinions about the integration of ITIL with managing projects that can take a long time to complete and might not actually be related or dependant on the IT infrastructure.

Thanks.
Cristiano
Back to top
View user's profile
Mark-OLoughlin
Senior Itiler


Joined: Oct 12, 2007
Posts: 306
Location: Ireland

PostPosted: Wed Apr 09, 2008 10:14 pm    Post subject: Reply with quote

Hi,

back up there for a moment. Just becuse a report does not exist it is not an incident or a problem. Can you have an Incident or a Problem about something that does not exist - interseting !!

My view is that it is a request - a user or department want a new report. That takes time, money and effort to Develop no Resolve.

I would see the initial requirement get logged as a Service Request and go through chnage management before being put into the live system. I do not see the eed to engane incident and/or problem management for this.
_________________
Mark O'Loughlin
ITSM / ITIL Consultant
Back to top
View user's profile
UrgentJensen
Senior Itiler


Joined: Feb 23, 2005
Posts: 458
Location: London

PostPosted: Wed Apr 09, 2008 11:50 pm    Post subject: Reply with quote

Hello there,

Yes you must certainly not mix service requests together with incidents. You could certainly use the same tool to log them but they will have entirely separate metrics/escalations etc.

Incidents: restoring service

Service Request: asking for a defined service e.g. new blackberry or new starter accounts.

Good luck,

UJ
_________________
Did I just say that out loud?

(Beige badge)
Back to top
View user's profile
cjmt
Itiler


Joined: Mar 14, 2008
Posts: 32
Location: Porto, PO.

PostPosted: Thu Apr 10, 2008 12:34 am    Post subject: Reply with quote

Thanks guys! It makes perfect sense.
I guess I didn't grasp the ITIL perspective on this.
So what could be the practical consequence of logging the two using the same tool? Statistics and reports might eventually get mixed if the tool doesn't allow intrinsically this distinction from the service desk interface, DYT?

Cheers,
Cristiano.
Back to top
View user's profile
UrgentJensen
Senior Itiler


Joined: Feb 23, 2005
Posts: 458
Location: London

PostPosted: Thu Apr 10, 2008 12:55 am    Post subject: Reply with quote

Quote:
'So what could be the practical consequence of logging the two using the same tool? Statistics and reports might eventually get mixed if the tool doesn't allow intrinsically this distinction from the service desk interface, DYT?'


Shouldn't happen... provided you set your up your categories to differentiate between incidents and requests.

You'd also need to give consideration to separate SLAs, escalations and resolver groups. In reality you don't have to treat them as completely alien work flows, they're not, just ensure you enable in your workflow tool to acknowledge the differences between them.

Then just design separate reports according to your requirements for both processes.

Cheers,

UJ
_________________
Did I just say that out loud?

(Beige badge)
Back to top
View user's profile
Diarmid
Senior Itiler


Joined: Mar 04, 2008
Posts: 1884
Location: Newcastle-under-Lyme

PostPosted: Thu Apr 10, 2008 2:00 am    Post subject: Reply with quote

Hi,

a service desk can take in lots of kinds of calls. You need to be able to classify on at least two levels, whether you call these call types or categories or anything else.

The top level activates at the moment you receive the call and should contain something like:

incident report
service request
change request
information request

After that you break the call down to something useful for how you manage these classifications (not urgency - that's another type of classification which you also need).

Don't let the nomenclature in your software tools lead you astray from proper and meaningful classifications.
_________________
"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
Back to top
View user's profile Send e-mail
cjmt
Itiler


Joined: Mar 14, 2008
Posts: 32
Location: Porto, PO.

PostPosted: Thu Apr 10, 2008 2:27 am    Post subject: Reply with quote

Diarmid,
Thanks, thats exactly the point to where I was going next, for I wasn't able, from the tool, to create a "classification" within each category. My initial thought is to try mapping the sub-categories as close as possible to the service catalog. Could this be an efficient approach?

Cheers.
Cristiano
Back to top
View user's profile
cjmt
Itiler


Joined: Mar 14, 2008
Posts: 32
Location: Porto, PO.

PostPosted: Thu Apr 10, 2008 2:57 am    Post subject: Reply with quote

Please ignore my question about categorization, it is closely related to a previous post in the Service Desk forum (post: "Incident Classifications - Clarification").
Thanks all.

Cristiano
Back to top
View user's profile
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.