<?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: Project Rhythm</title>
	<atom:link href="http://www.projectshrink.com/project-rhythm-1755.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.projectshrink.com/project-rhythm-1755.html</link>
	<description>Welcome To Shrinkonia.</description>
	<lastBuildDate>Thu, 09 Feb 2012 06:24:55 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Diwant Vaidya</title>
		<link>http://www.projectshrink.com/project-rhythm-1755.html#comment-1499</link>
		<dc:creator>Diwant Vaidya</dc:creator>
		<pubDate>Wed, 08 Jul 2009 19:34:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1755#comment-1499</guid>
		<description>@Dave Thanks for the response.  I was referring to one of the four &#039;commandments&#039; in the agile manifesto, &quot;software over documentation&quot;.  You are absolutely correct that certain agile ceremonies require documentation.  For example, we used to maintain a product backlog which was a simple excel.  Look at user stories as well.  Those are written on note cards.  So yes, there can be documentation in agile.  My point was that since agile supports &quot;software over documentation&quot;, if the documentation can be avoided entirely then a strict agilist would do so.  Teams of three people may do with zero documentation whatsoever!  It&#039;s a beautiful thing when it works, although it is only for teams that work well together.</description>
		<content:encoded><![CDATA[<p>@Dave Thanks for the response.  I was referring to one of the four &#8216;commandments&#8217; in the agile manifesto, &#8220;software over documentation&#8221;.  You are absolutely correct that certain agile ceremonies require documentation.  For example, we used to maintain a product backlog which was a simple excel.  Look at user stories as well.  Those are written on note cards.  So yes, there can be documentation in agile.  My point was that since agile supports &#8220;software over documentation&#8221;, if the documentation can be avoided entirely then a strict agilist would do so.  Teams of three people may do with zero documentation whatsoever!  It&#8217;s a beautiful thing when it works, although it is only for teams that work well together.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Nicolette</title>
		<link>http://www.projectshrink.com/project-rhythm-1755.html#comment-1498</link>
		<dc:creator>Dave Nicolette</dc:creator>
		<pubDate>Wed, 08 Jul 2009 02:30:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1755#comment-1498</guid>
		<description>Diwant&#039;s statement, &quot;In fact, strict agilists would say that nothing needs to be written in meetings as long as everyone is on the same page at the end,&quot; is not accurate. The daily stand-up is a particular &quot;agile&quot; ceremony that has a specific purpose. All meetings are not stand-up meetings. The statement that &quot;agilists&quot; think nothing needs to be written in (any) meeting reflects a poor understanding of agile methods.</description>
		<content:encoded><![CDATA[<p>Diwant&#8217;s statement, &#8220;In fact, strict agilists would say that nothing needs to be written in meetings as long as everyone is on the same page at the end,&#8221; is not accurate. The daily stand-up is a particular &#8220;agile&#8221; ceremony that has a specific purpose. All meetings are not stand-up meetings. The statement that &#8220;agilists&#8221; think nothing needs to be written in (any) meeting reflects a poor understanding of agile methods.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sanjay Kumar</title>
		<link>http://www.projectshrink.com/project-rhythm-1755.html#comment-1497</link>
		<dc:creator>Sanjay Kumar</dc:creator>
		<pubDate>Tue, 07 Jul 2009 07:22:43 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1755#comment-1497</guid>
		<description>Great post - Yes, It is very importent to have planned meetings with MOM artifact. But sometime in case of fire or to discuss point with small group standing meetings are also good way.</description>
		<content:encoded><![CDATA[<p>Great post &#8211; Yes, It is very importent to have planned meetings with MOM artifact. But sometime in case of fire or to discuss point with small group standing meetings are also good way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://www.projectshrink.com/project-rhythm-1755.html#comment-1496</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Tue, 07 Jul 2009 06:23:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1755#comment-1496</guid>
		<description>Hi all,

Glen Alleman posted a follow up article with the same name at

http://herdingcats.typepad.com/my_weblog/2009/06/project-rhythm.html

Check it out.</description>
		<content:encoded><![CDATA[<p>Hi all,</p>
<p>Glen Alleman posted a follow up article with the same name at</p>
<p><a href="http://herdingcats.typepad.com/my_weblog/2009/06/project-rhythm.html" rel="nofollow">http://herdingcats.typepad.com/my_weblog/2009/06/project-rhythm.html</a></p>
<p>Check it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diwant Vaidya</title>
		<link>http://www.projectshrink.com/project-rhythm-1755.html#comment-1495</link>
		<dc:creator>Diwant Vaidya</dc:creator>
		<pubDate>Mon, 06 Jul 2009 23:00:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1755#comment-1495</guid>
		<description>I disagree.  I used standups very effectively with my team.  In fact, strict agilists would say that nothing needs to be written in meetings as long as everyone is on the same page at the end.</description>
		<content:encoded><![CDATA[<p>I disagree.  I used standups very effectively with my team.  In fact, strict agilists would say that nothing needs to be written in meetings as long as everyone is on the same page at the end.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Endres</title>
		<link>http://www.projectshrink.com/project-rhythm-1755.html#comment-1494</link>
		<dc:creator>Ryan Endres</dc:creator>
		<pubDate>Thu, 02 Jul 2009 03:39:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1755#comment-1494</guid>
		<description>Great post! Yes rhythm is very important to keep our project teams focused on the project.</description>
		<content:encoded><![CDATA[<p>Great post! Yes rhythm is very important to keep our project teams focused on the project.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

