<?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"
	>
<channel>
	<title>Comments on: ITIL v3: Utility and Warranty - two sides of the same coin</title>
	<atom:link href="http://itilblues.wordpress.com/2007/12/14/itil-v3-utility-and-warranty-two-sides-of-the-same-coin/feed/" rel="self" type="application/rss+xml" />
	<link>http://itilblues.wordpress.com/2007/12/14/itil-v3-utility-and-warranty-two-sides-of-the-same-coin/</link>
	<description>ITIL rants and raves</description>
	<pubDate>Thu, 15 May 2008 23:50:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: ITIL</title>
		<link>http://itilblues.wordpress.com/2007/12/14/itil-v3-utility-and-warranty-two-sides-of-the-same-coin/#comment-436</link>
		<dc:creator>ITIL</dc:creator>
		<pubDate>Tue, 29 Jan 2008 09:05:18 +0000</pubDate>
		<guid isPermaLink="false">http://itilblues.wordpress.com/2007/12/14/itil-v3-utility-and-warranty-two-sides-of-the-same-coin/#comment-436</guid>
		<description>A very nice example of service utility and warranty - thanks.</description>
		<content:encoded><![CDATA[<p>A very nice example of service utility and warranty - thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bigapplezlp</title>
		<link>http://itilblues.wordpress.com/2007/12/14/itil-v3-utility-and-warranty-two-sides-of-the-same-coin/#comment-431</link>
		<dc:creator>bigapplezlp</dc:creator>
		<pubDate>Tue, 22 Jan 2008 02:29:49 +0000</pubDate>
		<guid isPermaLink="false">http://itilblues.wordpress.com/2007/12/14/itil-v3-utility-and-warranty-two-sides-of-the-same-coin/#comment-431</guid>
		<description>It's interesting to see that the non-functional aspects of a service has a generic name, Warranty, in ITIL v3. I totally agree that in the beginning, the customer will focus on Utility. After the functions were validated, the "experience" or the "Warranty" part of the service start to make the difference.</description>
		<content:encoded><![CDATA[<p>It&#8217;s interesting to see that the non-functional aspects of a service has a generic name, Warranty, in ITIL v3. I totally agree that in the beginning, the customer will focus on Utility. After the functions were validated, the &#8220;experience&#8221; or the &#8220;Warranty&#8221; part of the service start to make the difference.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
