<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2.1" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Do the Simplest Thing That Will Knock Their Socks Off</title>
	<link>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/</link>
	<description>A man needs a little madness, or else he never dares cut the rope and be free. -Nikos Kazantzakis</description>
	<pubDate>Thu, 20 Nov 2008 19:55:06 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.1</generator>

	<item>
		<title>By: Adrian Howard</title>
		<link>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/#comment-766</link>
		<author>Adrian Howard</author>
		<pubDate>Wed, 02 Aug 2006 15:02:52 +0000</pubDate>
		<guid>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/#comment-766</guid>
		<description>As I said on David's blog - I see it all of the time... and I  see it /more/ in agile groups than non-agile ones. 

I really don't see how an agile team can be less responsive than a non-agile ones. They get their feedback so much more quickly, and can respond to change so much more readily. 

Also, while "Getting Real" is still sitting in my to-read folder with a bazillion other things - my experience of the 37signals folks apps is that they're full of exactly those delightful little features that we're talking about...</description>
		<content:encoded><![CDATA[<p>As I said on David&#8217;s blog - I see it all of the time&#8230; and I  see it /more/ in agile groups than non-agile ones. </p>
<p>I really don&#8217;t see how an agile team can be less responsive than a non-agile ones. They get their feedback so much more quickly, and can respond to change so much more readily. </p>
<p>Also, while &#8220;Getting Real&#8221; is still sitting in my to-read folder with a bazillion other things - my experience of the 37signals folks apps is that they&#8217;re full of exactly those delightful little features that we&#8217;re talking about&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/#comment-764</link>
		<author>Daniel</author>
		<pubDate>Wed, 02 Aug 2006 10:03:18 +0000</pubDate>
		<guid>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/#comment-764</guid>
		<description>What I mean by "the agile keep it real approach" is not doing it unless requested and being aggressive in the features that you leave out. 

I am not saying that Agile projects can not include cool features.  But how often do you see bells and whistles given a high enough priority to get them done?  Outside of initiatives such as the &lt;a href="http://blogs.atlassian.com/developer/2006/06/fedex_day_3_part_1_confluence.html" rel="nofollow"&gt;Atlassian Fedex days&lt;/a&gt; I have not seen it happen.</description>
		<content:encoded><![CDATA[<p>What I mean by &#8220;the agile keep it real approach&#8221; is not doing it unless requested and being aggressive in the features that you leave out. </p>
<p>I am not saying that Agile projects can not include cool features.  But how often do you see bells and whistles given a high enough priority to get them done?  Outside of initiatives such as the <a href="http://blogs.atlassian.com/developer/2006/06/fedex_day_3_part_1_confluence.html" rel="nofollow">Atlassian Fedex days</a> I have not seen it happen.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pete</title>
		<link>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/#comment-762</link>
		<author>Pete</author>
		<pubDate>Wed, 02 Aug 2006 08:23:00 +0000</pubDate>
		<guid>http://www.alittlemadness.com/2006/08/02/do-the-simplest-thing-that-will-knock-their-socks-off/#comment-762</guid>
		<description>Not really sure what is meant by "the agile keep it real approach".

In an agile process you could select the features you want and implement them in an order of some priority that is important to you or the customer. That doesn't exclude cool features.

And who's to say an agile approach isn't used with iTunes.</description>
		<content:encoded><![CDATA[<p>Not really sure what is meant by &#8220;the agile keep it real approach&#8221;.</p>
<p>In an agile process you could select the features you want and implement them in an order of some priority that is important to you or the customer. That doesn&#8217;t exclude cool features.</p>
<p>And who&#8217;s to say an agile approach isn&#8217;t used with iTunes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
