<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Finally, a tight design argument against Agile</title>
	<link>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/</link>
	<description>apophenic pretentia</description>
	<pubDate>Sat, 13 Mar 2010 19:20:24 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Todd W.</title>
		<link>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/#comment-334</link>
		<pubDate>Mon, 31 Mar 2008 15:47:59 +0000</pubDate>
		<guid>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/#comment-334</guid>
					<description>I'm a huge fan of prototyping, at whatever level of fidelity, and I lament that I don't see enough of it or enough of it done seriously.  Though as you point out its important to match the audience and goals to the "truthfulness" or completeness of the prototype.

But the danger that's ever present and swallows up teams in no time is the temptation to lock on to the prototype as a solution and begin expending energy solving second-order problems, ie problems created by the prototype's failures to solve the original problem. They begin to spiral away from solving the original problem with Frankensteinian additions or subtractions to the prototype so that any sort of holistic consistency is completely lost.</description>
		<content:encoded><![CDATA[<p>I&#8217;m a huge fan of prototyping, at whatever level of fidelity, and I lament that I don&#8217;t see enough of it or enough of it done seriously.  Though as you point out its important to match the audience and goals to the &#8220;truthfulness&#8221; or completeness of the prototype.</p>
<p>But the danger that&#8217;s ever present and swallows up teams in no time is the temptation to lock on to the prototype as a solution and begin expending energy solving second-order problems, ie problems created by the prototype&#8217;s failures to solve the original problem. They begin to spiral away from solving the original problem with Frankensteinian additions or subtractions to the prototype so that any sort of holistic consistency is completely lost.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: kipbot</title>
		<link>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/#comment-307</link>
		<pubDate>Sat, 29 Mar 2008 16:00:32 +0000</pubDate>
		<guid>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/#comment-307</guid>
					<description>To be clear, I'm not opposed to agile per se, just the idea that it's the only/best way to do things.</description>
		<content:encoded><![CDATA[<p>To be clear, I&#8217;m not opposed to agile per se, just the idea that it&#8217;s the only/best way to do things.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Damon Poole</title>
		<link>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/#comment-305</link>
		<pubDate>Sat, 29 Mar 2008 14:43:49 +0000</pubDate>
		<guid>http://www.kipbot.com/blog/2008/03/29/finally-a-tight-design-argument-against-agile/#comment-305</guid>
					<description>Hi,

I know what you mean about the zealotry. That was my initial experience as well. It took me a while to realize that many of the ideas themselves are sound, even if some of the proponents are foaming at the mouth.

You may be interested in the following post on design:
http://damonpoole.blogspot.com/2007/12/desiging-software-is-same-as-predicting.html

I agree that "doing it right" is important, but it isn't always clear what is needed. So, you can spend lots of time "doing it right" only to have somebody say "that works great, but it isn't what I wanted at all."</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I know what you mean about the zealotry. That was my initial experience as well. It took me a while to realize that many of the ideas themselves are sound, even if some of the proponents are foaming at the mouth.</p>
<p>You may be interested in the following post on design:<br />
<a href="http://damonpoole.blogspot.com/2007/12/desiging-software-is-same-as-predicting.html" rel="nofollow">http://damonpoole.blogspot.com/2007/12/desiging-software-is-same-as-predicting.html</a></p>
<p>I agree that &#8220;doing it right&#8221; is important, but it isn&#8217;t always clear what is needed. So, you can spend lots of time &#8220;doing it right&#8221; only to have somebody say &#8220;that works great, but it isn&#8217;t what I wanted at all.&#8221;
</p>
]]></content:encoded>
				</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.766 seconds -->
