<?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: 4 Steps for Organizational Agility</title>
	<atom:link href="http://merchantstand.com/2009/07/4-steps-for-organizational-agility/feed/" rel="self" type="application/rss+xml" />
	<link>http://merchantstand.com/2009/07/4-steps-for-organizational-agility/</link>
	<description>A Marketing Technology Place</description>
	<lastBuildDate>Fri, 03 Feb 2012 12:00:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Bob Williams</title>
		<link>http://merchantstand.com/2009/07/4-steps-for-organizational-agility/comment-page-1/#comment-106</link>
		<dc:creator>Bob Williams</dc:creator>
		<pubDate>Mon, 13 Jul 2009 23:42:51 +0000</pubDate>
		<guid isPermaLink="false">http://merchantstand.com/?p=462#comment-106</guid>
		<description>My experience with trying to incrementally change development teams towards an agile process has not been favorable. Of course I never achieved management support either, so it was doomed from the start. What happened in the end was they renamed the enhancement list to a backlog. Then they said they wanted to target 10 week release cycles. In the end, the release date was determined after going through requirements, analysis, and estimates. 

I think on a team-by-team or process-by-process basis it would be easier to change out the system wholesale. But it&#039;ll only work if you get management on board and the team members trained and behind it. (Steps 2 and 3).</description>
		<content:encoded><![CDATA[<p>My experience with trying to incrementally change development teams towards an agile process has not been favorable. Of course I never achieved management support either, so it was doomed from the start. What happened in the end was they renamed the enhancement list to a backlog. Then they said they wanted to target 10 week release cycles. In the end, the release date was determined after going through requirements, analysis, and estimates. </p>
<p>I think on a team-by-team or process-by-process basis it would be easier to change out the system wholesale. But it&#8217;ll only work if you get management on board and the team members trained and behind it. (Steps 2 and 3).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Cardarella</title>
		<link>http://merchantstand.com/2009/07/4-steps-for-organizational-agility/comment-page-1/#comment-105</link>
		<dc:creator>Brian Cardarella</dc:creator>
		<pubDate>Mon, 13 Jul 2009 17:59:05 +0000</pubDate>
		<guid isPermaLink="false">http://merchantstand.com/?p=462#comment-105</guid>
		<description>What are your thoughts on migrating a team to agile processes? I agree that people become comfortable with the tools they use. Personally, I think that becomes a very big issue when you try to change too much of the process. Ultimately one can be &#039;more efficient&#039; doing it a particular way but the downtime of changing too much might not jive with business. Also, one might reject the &#039;new way&#039; if there is too much change because they are not feeling productive. I&#039;d like to hear thoughts on how much new process can be introduced to a team at a time. Or has there been success with just going cold turkey?</description>
		<content:encoded><![CDATA[<p>What are your thoughts on migrating a team to agile processes? I agree that people become comfortable with the tools they use. Personally, I think that becomes a very big issue when you try to change too much of the process. Ultimately one can be &#8216;more efficient&#8217; doing it a particular way but the downtime of changing too much might not jive with business. Also, one might reject the &#8216;new way&#8217; if there is too much change because they are not feeling productive. I&#8217;d like to hear thoughts on how much new process can be introduced to a team at a time. Or has there been success with just going cold turkey?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

