<?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: BMC Acquires VaraLogix, Releases Version 3.0 of CLM</title>
	<atom:link href="http://diversity.net.nz/bmc-acquires-varalogix-releases-version-3-0-of-clm/2012/08/09/feed/" rel="self" type="application/rss+xml" />
	<link>http://diversity.net.nz/bmc-acquires-varalogix-releases-version-3-0-of-clm/2012/08/09/</link>
	<description>Thoughts on the Future of Business and User-Centered Technology</description>
	<lastBuildDate>Tue, 18 Jun 2013 06:31:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Brent Knipfer</title>
		<link>http://diversity.net.nz/bmc-acquires-varalogix-releases-version-3-0-of-clm/2012/08/09/comment-page-1/#comment-138346</link>
		<dc:creator>Brent Knipfer</dc:creator>
		<pubDate>Tue, 13 Nov 2012 12:12:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.diversity.net.nz/?p=8964#comment-138346</guid>
		<description><![CDATA[If DevOps means both development and operations subscribe to common policies, processes, procedures, work instructions including delegation of duties (simply different people for do versus check activities), then any set of tools will work.  The constant fixation on tools to &#039;make&#039; people do something will repeat failure history again.  Development leadership lack governance control or operationa experience to realize the need for release management. The moniker might have been better made OpDev to indicate who is really service who.  The value of new capability is only realized in Operations. What companies are practicing integrated release management across development and operations? Another chasm is a failure to define and manage well with the tools that CLM will eventually give orders to first. To succeed the layer under CLM must run 6 months in operations with the standards that CLM will enforce before trying to implement CLM.]]></description>
		<content:encoded><![CDATA[<p>If DevOps means both development and operations subscribe to common policies, processes, procedures, work instructions including delegation of duties (simply different people for do versus check activities), then any set of tools will work.  The constant fixation on tools to &#8216;make&#8217; people do something will repeat failure history again.  Development leadership lack governance control or operationa experience to realize the need for release management. The moniker might have been better made OpDev to indicate who is really service who.  The value of new capability is only realized in Operations. What companies are practicing integrated release management across development and operations? Another chasm is a failure to define and manage well with the tools that CLM will eventually give orders to first. To succeed the layer under CLM must run 6 months in operations with the standards that CLM will enforce before trying to implement CLM.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
