<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: ITIL® v3 One Year On</title>
	<atom:link href="http://foxit.wordpress.com/2008/07/15/itil-v3-one-year-on/feed/" rel="self" type="application/rss+xml" />
	<link>http://foxit.wordpress.com/2008/07/15/itil-v3-one-year-on/</link>
	<description>The Authority in Service Management™</description>
	<lastBuildDate>Thu, 31 Jul 2008 00:17:30 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kurt Richardson</title>
		<link>http://foxit.wordpress.com/2008/07/15/itil-v3-one-year-on/#comment-243</link>
		<dc:creator>Kurt Richardson</dc:creator>
		<pubDate>Thu, 31 Jul 2008 00:17:30 +0000</pubDate>
		<guid isPermaLink="false">http://foxit.wordpress.com/?p=19#comment-243</guid>
		<description>My skepticism on v.3 lifted in the last few weeks.  Many months were spent convincing our CIO to fund an ITIL v.2 program without much luck.  His response could best be described as polite indifference until we built utility maps for a pair of our mission-critical services.  Viola, on came the lights.  That material alone made it worth sloshing through the strategy book.</description>
		<content:encoded><![CDATA[<p>My skepticism on v.3 lifted in the last few weeks.  Many months were spent convincing our CIO to fund an ITIL v.2 program without much luck.  His response could best be described as polite indifference until we built utility maps for a pair of our mission-critical services.  Viola, on came the lights.  That material alone made it worth sloshing through the strategy book.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
