<?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 for Agile Focus</title>
	<atom:link href="http://agilefocus.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilefocus.com</link>
	<description>A group weblog for and about Agile software development</description>
	<pubDate>Fri, 12 Mar 2010 05:31:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on 9 Signs of Bad Team Spaces by Decreased Productivity in Open Floor Plan vs. Scrum and Agile &#171; Spare Cycles</title>
		<link>http://agilefocus.com/2010/02/15/9-signs-of-bad-team-spaces/comment-page-1/#comment-757</link>
		<dc:creator>Decreased Productivity in Open Floor Plan vs. Scrum and Agile &#171; Spare Cycles</dc:creator>
		<pubDate>Tue, 23 Feb 2010 20:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=270#comment-757</guid>
		<description>[...] William Pietri commented recently on one of the top signs of a poorly functioning scrum space is people wearing headphones. I think that people wearing headphones is a direct result of team members trying to combat noise [...]</description>
		<content:encoded><![CDATA[<p>[...] William Pietri commented recently on one of the top signs of a poorly functioning scrum space is people wearing headphones. I think that people wearing headphones is a direct result of team members trying to combat noise [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 9 Signs of Bad Team Spaces by William Pietri</title>
		<link>http://agilefocus.com/2010/02/15/9-signs-of-bad-team-spaces/comment-page-1/#comment-754</link>
		<dc:creator>William Pietri</dc:creator>
		<pubDate>Wed, 17 Feb 2010 17:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=270#comment-754</guid>
		<description>@CTheB: Thanks for the comment.

Regarding headphones, I think it depends on the kind of work you're doing. If you don't need to be in touch with the people around you, by all means listen to music. But this being a blog about Agile software development, which is a team-oriented approach, I believe that not needing to be in touch with the people around you is often a sign of a problem.

That's not to say one should never do it. Sometimes people really need to do a bit of solo work. In which case, sure, wear headphones. Or, better, go somewhere else for a bit. But as a general rule, people not being present in the team room is a bad sign, whether that's physically or just mentally.</description>
		<content:encoded><![CDATA[<p>@CTheB: Thanks for the comment.</p>
<p>Regarding headphones, I think it depends on the kind of work you&#8217;re doing. If you don&#8217;t need to be in touch with the people around you, by all means listen to music. But this being a blog about Agile software development, which is a team-oriented approach, I believe that not needing to be in touch with the people around you is often a sign of a problem.</p>
<p>That&#8217;s not to say one should never do it. Sometimes people really need to do a bit of solo work. In which case, sure, wear headphones. Or, better, go somewhere else for a bit. But as a general rule, people not being present in the team room is a bad sign, whether that&#8217;s physically or just mentally.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 9 Signs of Bad Team Spaces by CTheB</title>
		<link>http://agilefocus.com/2010/02/15/9-signs-of-bad-team-spaces/comment-page-1/#comment-753</link>
		<dc:creator>CTheB</dc:creator>
		<pubDate>Wed, 17 Feb 2010 17:25:14 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=270#comment-753</guid>
		<description>Number 1 is wrong as a sign of a bad space.  It presupposes that people don't listen to music while they work because they enjoy it or for any reason other than to tune out some distraction(s). While it may be true that some people listen to music to tune out distractions, whether all or some of the time, that doesn't mean that that's the case with everyone or all the time.  What the point should say is that one should identify whether or not there is something negative causing people to listen to music and if there is one (or many) to deal with them.

I tend to spend an hour or two a day, sometimes more, listening to music while I work.  Why?  Well, mostly because I enjoy listening to music.  That's why I have it.  Sometimes it's because I'm preparing for a set and having it playing in the background helps me get more familiar with it.  Every now and then it's because something is distracting or annoying me.

The rest I agree with.</description>
		<content:encoded><![CDATA[<p>Number 1 is wrong as a sign of a bad space.  It presupposes that people don&#8217;t listen to music while they work because they enjoy it or for any reason other than to tune out some distraction(s). While it may be true that some people listen to music to tune out distractions, whether all or some of the time, that doesn&#8217;t mean that that&#8217;s the case with everyone or all the time.  What the point should say is that one should identify whether or not there is something negative causing people to listen to music and if there is one (or many) to deal with them.</p>
<p>I tend to spend an hour or two a day, sometimes more, listening to music while I work.  Why?  Well, mostly because I enjoy listening to music.  That&#8217;s why I have it.  Sometimes it&#8217;s because I&#8217;m preparing for a set and having it playing in the background helps me get more familiar with it.  Every now and then it&#8217;s because something is distracting or annoying me.</p>
<p>The rest I agree with.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 9 Signs of Bad Team Spaces by William Pietri</title>
		<link>http://agilefocus.com/2010/02/15/9-signs-of-bad-team-spaces/comment-page-1/#comment-752</link>
		<dc:creator>William Pietri</dc:creator>
		<pubDate>Wed, 17 Feb 2010 04:56:31 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=270#comment-752</guid>
		<description>Excellent point, Rick. Now that you mention it, I've seen that pattern, too.</description>
		<content:encoded><![CDATA[<p>Excellent point, Rick. Now that you mention it, I&#8217;ve seen that pattern, too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 9 Signs of Bad Team Spaces by Rick Tonoli</title>
		<link>http://agilefocus.com/2010/02/15/9-signs-of-bad-team-spaces/comment-page-1/#comment-751</link>
		<dc:creator>Rick Tonoli</dc:creator>
		<pubDate>Tue, 16 Feb 2010 19:49:28 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=270#comment-751</guid>
		<description>How about: Excessive tea/coffee/smoke breaks - I've found a correlation between frequency and duration of "breaks", and general morale of the team.</description>
		<content:encoded><![CDATA[<p>How about: Excessive tea/coffee/smoke breaks - I&#8217;ve found a correlation between frequency and duration of &#8220;breaks&#8221;, and general morale of the team.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 10 rules for great development spaces by Agile Focus &#187; Blog Archive &#187; 9 Signs of Bad Team Spaces</title>
		<link>http://agilefocus.com/2009/04/20/10-rules-for-great-development-spaces/comment-page-1/#comment-750</link>
		<dc:creator>Agile Focus &#187; Blog Archive &#187; 9 Signs of Bad Team Spaces</dc:creator>
		<pubDate>Tue, 16 Feb 2010 06:17:50 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=259#comment-750</guid>
		<description>[...] of the most popular articles here is 10 Rules For Great Development Spaces, so I thought I&#8217;d follow up by explicitly listing signs of bad spaces. These are my top 9, [...]</description>
		<content:encoded><![CDATA[<p>[...] of the most popular articles here is 10 Rules For Great Development Spaces, so I thought I&#8217;d follow up by explicitly listing signs of bad spaces. These are my top 9, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 21 ways to hate pair programming by Andrew</title>
		<link>http://agilefocus.com/2009/01/06/21-ways-to-hate-pair-programming/comment-page-1/#comment-747</link>
		<dc:creator>Andrew</dc:creator>
		<pubDate>Fri, 01 Jan 2010 15:57:08 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=197#comment-747</guid>
		<description>Great list! Really good amplification. I'm guilty of 1 and 21. I think pair programming must start from this list.</description>
		<content:encoded><![CDATA[<p>Great list! Really good amplification. I&#8217;m guilty of 1 and 21. I think pair programming must start from this list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on 21 ways to hate pair programming by aimee.mychores.co.uk</title>
		<link>http://agilefocus.com/2009/01/06/21-ways-to-hate-pair-programming/comment-page-1/#comment-743</link>
		<dc:creator>aimee.mychores.co.uk</dc:creator>
		<pubDate>Sun, 22 Nov 2009 11:21:01 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=197#comment-743</guid>
		<description>Really good list. I suffer from different mistakes depending who i'm pairing with.

One of my worst habits is not on your list:

Dictate to your pair. Because you are awesome and your partner is just a secretary to type your wonderful code for you!</description>
		<content:encoded><![CDATA[<p>Really good list. I suffer from different mistakes depending who i&#8217;m pairing with.</p>
<p>One of my worst habits is not on your list:</p>
<p>Dictate to your pair. Because you are awesome and your partner is just a secretary to type your wonderful code for you!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The myth of &#8220;undesigned&#8221; by William Pietri</title>
		<link>http://agilefocus.com/2009/09/14/the-myth-of-undesigned/comment-page-1/#comment-741</link>
		<dc:creator>William Pietri</dc:creator>
		<pubDate>Fri, 18 Sep 2009 07:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=445#comment-741</guid>
		<description>Hi, Jeffery. That was exactly the point I was trying to make. Except I'm taking it one step further. The source code is the design, but the finished artifact is the running software, not just the object code.</description>
		<content:encoded><![CDATA[<p>Hi, Jeffery. That was exactly the point I was trying to make. Except I&#8217;m taking it one step further. The source code is the design, but the finished artifact is the running software, not just the object code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The myth of &#8220;undesigned&#8221; by Jeffrey Aguilera</title>
		<link>http://agilefocus.com/2009/09/14/the-myth-of-undesigned/comment-page-1/#comment-740</link>
		<dc:creator>Jeffrey Aguilera</dc:creator>
		<pubDate>Fri, 18 Sep 2009 04:06:18 +0000</pubDate>
		<guid isPermaLink="false">http://agilefocus.com/?p=445#comment-740</guid>
		<description>"One group of people makes up some blueprints, and then an entirely different group of people makes physical objects.  That second group is judged not by the utility of the objects, but by conformance to the design."

It's not that this analogy is wrong for software.  The analogy is apt.  But the second group has been entirely automated (by members of the first group.) The second group is the compiler and build tools ... and yes, the compiler is judged based on its conformance to the design (i.e., software.)</description>
		<content:encoded><![CDATA[<p>&#8220;One group of people makes up some blueprints, and then an entirely different group of people makes physical objects.  That second group is judged not by the utility of the objects, but by conformance to the design.&#8221;</p>
<p>It&#8217;s not that this analogy is wrong for software.  The analogy is apt.  But the second group has been entirely automated (by members of the first group.) The second group is the compiler and build tools &#8230; and yes, the compiler is judged based on its conformance to the design (i.e., software.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
