<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The benefits of describing ITIL incidents in object-deviation format</title>
	<atom:link href="http://blog.kathyreid.id.au/2008/10/18/the-benefits-of-describing-itil-incidents-in-object-deviation-format/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.kathyreid.id.au/2008/10/18/the-benefits-of-describing-itil-incidents-in-object-deviation-format/</link>
	<description>Posts on ITIL, Kepner Tregoe, knitting, PHP and other free and open source (FOSS) tools</description>
	<lastBuildDate>Mon, 19 Jul 2010 11:25:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Alec Clews</title>
		<link>http://blog.kathyreid.id.au/2008/10/18/the-benefits-of-describing-itil-incidents-in-object-deviation-format/comment-page-1/#comment-1212</link>
		<dc:creator>Alec Clews</dc:creator>
		<pubDate>Fri, 05 Dec 2008 04:07:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kathyreid.id.au/?p=66#comment-1212</guid>
		<description>An excellent post. It&#039;s also a good idea to have a standard set of terms to be used by the agent when writing the object and deviation

If these term (the object names or descriptions) can correspond to the terms used to describe the IT components and services in the ITIL libraries, config system etc. as far as *practical*  it helps avoid further confusion.

However don&#039;t over burden the user with the jargon of course.

I guess the final point is that there needs to be a clear correspondence (a translation table?) between the terms used by the incident desk with the users and the nomenclature used in the rest of the ITIL processes.</description>
		<content:encoded><![CDATA[<p>An excellent post. It&#8217;s also a good idea to have a standard set of terms to be used by the agent when writing the object and deviation</p>
<p>If these term (the object names or descriptions) can correspond to the terms used to describe the IT components and services in the ITIL libraries, config system etc. as far as *practical*  it helps avoid further confusion.</p>
<p>However don&#8217;t over burden the user with the jargon of course.</p>
<p>I guess the final point is that there needs to be a clear correspondence (a translation table?) between the terms used by the incident desk with the users and the nomenclature used in the rest of the ITIL processes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Borwick</title>
		<link>http://blog.kathyreid.id.au/2008/10/18/the-benefits-of-describing-itil-incidents-in-object-deviation-format/comment-page-1/#comment-1134</link>
		<dc:creator>John Borwick</dc:creator>
		<pubDate>Mon, 10 Nov 2008 19:01:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.kathyreid.id.au/?p=66#comment-1134</guid>
		<description>Thanks for this post.  This technique for standardizing and clarifying an incident summary could help us as we improve our incident management procedure.  FYI we&#039;ve also cited you at http://itsm.is.wfu.edu/node/100 :-)</description>
		<content:encoded><![CDATA[<p>Thanks for this post.  This technique for standardizing and clarifying an incident summary could help us as we improve our incident management procedure.  FYI we&#8217;ve also cited you at <a href="http://itsm.is.wfu.edu/node/100" rel="nofollow">http://itsm.is.wfu.edu/node/100</a> <img src='http://blog.kathyreid.id.au/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
