 




<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Overheard in the tech blogosphere &#187; release management</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/overheard/tag/release-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/overheard</link>
	<description>A Whatis.com blog</description>
	<lastBuildDate>Tue, 19 Feb 2013 14:32:17 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>Release management &#8211; the IT equivalent of herding cats</title>
		<link>http://itknowledgeexchange.techtarget.com/overheard/release-management-the-it-equivalent-of-herding-cats/</link>
		<comments>http://itknowledgeexchange.techtarget.com/overheard/release-management-the-it-equivalent-of-herding-cats/#comments</comments>
		<pubDate>Fri, 12 Jun 2009 16:28:27 +0000</pubDate>
		<dc:creator>Margaret Rouse</dc:creator>
				<category><![CDATA[IT Governance]]></category>
		<category><![CDATA[ITIL]]></category>
		<category><![CDATA[Project management]]></category>
		<category><![CDATA[release management]]></category>

		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/overheard/?p=2566</guid>
		<description><![CDATA[Studies have shown us that a large majority of IT projects fail either in part or outright for non-technical reasons that could have been prevented with proper planning. George Spafford, Release policies set standards for rollouts Today&#8217;s WhatIs.com Word of the Day is release management. As part of a webcast on Understanding the ITIL Trinity [...]]]></description>
				<content:encoded><![CDATA[<table border="0" cellspacing="5" cellpadding="5">
<tbody>
<tr>
<td><a href="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/8/files/2009/06/gspafford-sm.jpg"><img class="alignnone size-medium wp-image-2565" src="http://cdn.ttgtmedia.com/ITKE/uploads/blogs.dir/8/files/2009/06/gspafford-sm.jpg" alt="" /></a></td>
<td><span class="a3">Studies have shown us that a large majority of IT projects fail either in part or outright for non-technical reasons that could have been prevented with proper planning. </span></p>
<p>George Spafford, <a href="http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1276252_mem1,00.html">Release policies set standards for rollouts</a></td>
</tr>
</tbody>
</table>
<p>Today&#8217;s WhatIs.com Word of the Day is <a href="http://searchsystemschannel.techtarget.com/sDefinition/0,,sid99_gci1319000,00.html">release management</a>.</p>
<p>As part of a <a href="http://solutions.internet.com/3656_default">webcast</a> on Understanding the ITIL Trinity of Configuration Change and Release Management, George says that:</p>
<ul>
<li> 29% of projects deliver on-time with expected features</li>
<li>53% are challenged (are delivered on-time without expected features)</li>
<li>18% outright fail outright</li>
</ul>
<p>It&#8217;s not surprising that George attributes these dismal numbers to non-technical factors, including lack of project planning, poor requirements definition, not getting the right stakeholders involved,  poor communication and insufficient management oversight.</p>
<p>I&#8217;m frankly surprised that the number of projects that deliver on-time with expected features is so high.  I would have guessed&#8230;3%.</p>
<!-- wpms-network-global-inserts -->]]></content:encoded>
			<wfw:commentRss>http://itknowledgeexchange.techtarget.com/overheard/release-management-the-it-equivalent-of-herding-cats/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
