<?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: Implementing Agile: Five Warning Signs for CIOs</title>
	<atom:link href="http://www.ciopedia.com/2009/05/implementing-agile-warning-signs-for-cios/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ciopedia.com/2009/05/implementing-agile-warning-signs-for-cios/</link>
	<description></description>
	<lastBuildDate>Thu, 02 Sep 2010 18:18:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Vin D'Amico</title>
		<link>http://www.ciopedia.com/2009/05/implementing-agile-warning-signs-for-cios/#comment-28</link>
		<dc:creator>Vin D'Amico</dc:creator>
		<pubDate>Thu, 28 May 2009 17:16:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciopedia.com/?p=864#comment-28</guid>
		<description>Good advice for companies trying agile development:

from Twitter: http://twitter.com/brainslink</description>
		<content:encoded><![CDATA[<p>Good advice for companies trying agile development:</p>
<p>from Twitter: <a href="http://twitter.com/brainslink" rel="nofollow">http://twitter.com/brainslink</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Moore</title>
		<link>http://www.ciopedia.com/2009/05/implementing-agile-warning-signs-for-cios/#comment-26</link>
		<dc:creator>John Moore</dc:creator>
		<pubDate>Mon, 04 May 2009 23:37:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.ciopedia.com/?p=864#comment-26</guid>
		<description>Well said.  Any process must be improve your overall efficiency and not be done simply because &quot;that&#039;s the way you do agile&quot;.  As always:

-  Ensure that processes are documented.
-  Processes must be repeatable (part of reason to document).
-  Measures of success should be defined.
-  Training, and retraining, should be defined for new hires and for internal staff.

I love your point about being overly dogmatic.  It&#039;s the best way to take a great idea or process and destroy it.

John Moore
http://twitter.com/JohnFMoore</description>
		<content:encoded><![CDATA[<p>Well said.  Any process must be improve your overall efficiency and not be done simply because &#8220;that&#8217;s the way you do agile&#8221;.  As always:</p>
<p>-  Ensure that processes are documented.<br />
-  Processes must be repeatable (part of reason to document).<br />
-  Measures of success should be defined.<br />
-  Training, and retraining, should be defined for new hires and for internal staff.</p>
<p>I love your point about being overly dogmatic.  It&#8217;s the best way to take a great idea or process and destroy it.</p>
<p>John Moore<br />
<a href="http://twitter.com/JohnFMoore" rel="nofollow">http://twitter.com/JohnFMoore</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

