<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Agile Planning Tools: The Spreadsheet Strawman</title>
	<link>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/</link>
	<description></description>
	<pubDate>Tue, 06 Jan 2009 03:27:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.1</generator>

	<item>
		<title>by: Steve Bate</title>
		<link>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/#comment-319</link>
		<pubDate>Wed, 09 Aug 2006 05:27:29 +0000</pubDate>
		<guid>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/#comment-319</guid>
					<description>Hi Dave,

I agree about the multiple levels of planning and how cards can be more useful at one level than another. That's what I was referring to when I spoke of using cards with online tools (possible for different aspects of the planning activity, as you described). I also have had the same experience with XPlanner or similar tools and the stakeholder appreciation for the status transparency without needing to be in the development room.

On the agile perspective...

I agree there is no official definition of the &quot;agile perspective&quot;. Perhaps I should have written &quot;the opinions of recognized XP/Agile thought leaders&quot;. I included quotes from a small sampling of those thought leaders so I don't think it's fair to say this is not a significant perspective within the XP/Agile communities. However, I agree the wording implies an possible over generalization to the agile community at large. I'll be more careful in the future.

Thanks for keeping me accurate. :-)

Steve</description>
		<content:encoded><![CDATA[<p>Hi Dave,</p>
<p>I agree about the multiple levels of planning and how cards can be more useful at one level than another. That&#8217;s what I was referring to when I spoke of using cards with online tools (possible for different aspects of the planning activity, as you described). I also have had the same experience with XPlanner or similar tools and the stakeholder appreciation for the status transparency without needing to be in the development room.</p>
<p>On the agile perspective&#8230;</p>
<p>I agree there is no official definition of the &#8220;agile perspective&#8221;. Perhaps I should have written &#8220;the opinions of recognized XP/Agile thought leaders&#8221;. I included quotes from a small sampling of those thought leaders so I don&#8217;t think it&#8217;s fair to say this is not a significant perspective within the XP/Agile communities. However, I agree the wording implies an possible over generalization to the agile community at large. I&#8217;ll be more careful in the future.</p>
<p>Thanks for keeping me accurate. <img src='http://blog.technoetic.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Steve
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Dave Nicolette</title>
		<link>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/#comment-316</link>
		<pubDate>Tue, 08 Aug 2006 19:56:32 +0000</pubDate>
		<guid>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/#comment-316</guid>
					<description>&amp;#62;The party line in XP/Agile is that note cards are the best planning tool. 

I don't know about party lines, but I do know there's more than one level of planning involved in a project. Note cards can be useful for very short term planning. For longer term planning - iteration, release, project, strategic - seems like note cards would be pretty cumbersome and error-prone.

On some projects, I've found customers like a tool like XPlanner because they can check on the status of their project at any time. If the team used note cards and literally nothing else, the customer would have to go to the work area in person to see the status of the project. Not very convenient in many cases.

&amp;#62;It’s not clear if the Agile perspective in this case is a lack of imagination or a lack of experience. 

What you describe in this portion of your post hardly represents &quot;the agile perspective.&quot; Interesting that you mention strawman arguments in other contexts, indicating that you know what they are. And yet, this. Interesting. Maybe the strawman is in the eye of the beholder.</description>
		<content:encoded><![CDATA[<p>&gt;The party line in XP/Agile is that note cards are the best planning tool. </p>
<p>I don&#8217;t know about party lines, but I do know there&#8217;s more than one level of planning involved in a project. Note cards can be useful for very short term planning. For longer term planning - iteration, release, project, strategic - seems like note cards would be pretty cumbersome and error-prone.</p>
<p>On some projects, I&#8217;ve found customers like a tool like XPlanner because they can check on the status of their project at any time. If the team used note cards and literally nothing else, the customer would have to go to the work area in person to see the status of the project. Not very convenient in many cases.</p>
<p>&gt;It’s not clear if the Agile perspective in this case is a lack of imagination or a lack of experience. </p>
<p>What you describe in this portion of your post hardly represents &#8220;the agile perspective.&#8221; Interesting that you mention strawman arguments in other contexts, indicating that you know what they are. And yet, this. Interesting. Maybe the strawman is in the eye of the beholder.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Timothy Johnson</title>
		<link>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/#comment-307</link>
		<pubDate>Mon, 07 Aug 2006 01:11:21 +0000</pubDate>
		<guid>http://blog.technoetic.com/2006/08/05/agile-planning-tools-the-spreadsheet-strawman/#comment-307</guid>
					<description>Relevant post, Steve.  I've commented on tool selection before in my blog (see my post entitled &quot;tool softener&quot;) but you've captured the pertinent issue of tool's role in communication quite nicely (along with the other human dynamics).  Glad I found your blog.  Great writing.</description>
		<content:encoded><![CDATA[<p>Relevant post, Steve.  I&#8217;ve commented on tool selection before in my blog (see my post entitled &#8220;tool softener&#8221;) but you&#8217;ve captured the pertinent issue of tool&#8217;s role in communication quite nicely (along with the other human dynamics).  Glad I found your blog.  Great writing.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
