<?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: Small Steps Are Good; Be Careful What You Call Those Steps</title>
	<atom:link href="http://www.jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<lastBuildDate>Fri, 18 May 2012 15:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Agile Projects Need Full Commitment - PM Hut</title>
		<link>http://www.jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html/comment-page-1#comment-63565</link>
		<dc:creator>Agile Projects Need Full Commitment - PM Hut</dc:creator>
		<pubDate>Tue, 15 Dec 2009 15:27:17 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8782#comment-63565</guid>
		<description>[...] The original article can be found at: http://jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html [...]</description>
		<content:encoded><![CDATA[<p>[...] The original article can be found at: <a href="http://jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html" rel="nofollow">http://jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: سیاره مدیریت پروژه فارسی &#187; Blog Archive &#187; Plunge In or Dip Your Toe? (for Managers)</title>
		<link>http://www.jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html/comment-page-1#comment-52861</link>
		<dc:creator>سیاره مدیریت پروژه فارسی &#187; Blog Archive &#187; Plunge In or Dip Your Toe? (for Managers)</dc:creator>
		<pubDate>Wed, 22 Jul 2009 00:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8782#comment-52861</guid>
		<description>[...] the Small Steps and Plunge In posts, I said projects should transition to agile all the way. But does it work the [...]</description>
		<content:encoded><![CDATA[<p>[...] the Small Steps and Plunge In posts, I said projects should transition to agile all the way. But does it work the [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pradeep Bhanot</title>
		<link>http://www.jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html/comment-page-1#comment-52590</link>
		<dc:creator>Pradeep Bhanot</dc:creator>
		<pubDate>Wed, 15 Jul 2009 16:40:42 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8782#comment-52590</guid>
		<description>Johanna,
 I too am a proponent of incremental development strategies having practiced them for decades.  

Agile is more than a fad. I have seen it used with success in projects that take a hybrid approach by using traditional methods to structure the macro project plan, but employ agile for key deliverables that are time critical and require intense customer participation. 

As you state, traditional development methods are maturing to adopt continuous build and integration and have started to pass more builds to QA at earlier stages of development to save time, but that is not enough to be termed agile.</description>
		<content:encoded><![CDATA[<p>Johanna,<br />
 I too am a proponent of incremental development strategies having practiced them for decades.  </p>
<p>Agile is more than a fad. I have seen it used with success in projects that take a hybrid approach by using traditional methods to structure the macro project plan, but employ agile for key deliverables that are time critical and require intense customer participation. </p>
<p>As you state, traditional development methods are maturing to adopt continuous build and integration and have started to pass more builds to QA at earlier stages of development to save time, but that is not enough to be termed agile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rick</title>
		<link>http://www.jrothman.com/blog/mpd/2009/07/small-steps-are-good-be-careful-what-you-call-those-steps.html/comment-page-1#comment-52553</link>
		<dc:creator>rick</dc:creator>
		<pubDate>Tue, 14 Jul 2009 23:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8782#comment-52553</guid>
		<description>There are at least 2 reasons to be picky about terminology: 

1) &quot;Why isn&#039;t this agile stuff working?&quot; - from management if a partially implemented process isn&#039;t producing the results promised by agile. 

2) Clarity when hiring and training people. Don&#039;t insist on new hires having experience with agile when you&#039;ve not moved to agile. Makes you look foolish and starts the off with the thought &quot;these people don&#039;t know what they&#039;re talking about&quot; or &quot;will say anything to sound good.&quot;</description>
		<content:encoded><![CDATA[<p>There are at least 2 reasons to be picky about terminology: </p>
<p>1) &#8220;Why isn&#8217;t this agile stuff working?&#8221; &#8211; from management if a partially implemented process isn&#8217;t producing the results promised by agile. </p>
<p>2) Clarity when hiring and training people. Don&#8217;t insist on new hires having experience with agile when you&#8217;ve not moved to agile. Makes you look foolish and starts the off with the thought &#8220;these people don&#8217;t know what they&#8217;re talking about&#8221; or &#8220;will say anything to sound good.&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

