<?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: Anti agile words: weekly</title>
	<atom:link href="http://www.the-arm.com/2008/06/anti-agile-words-weekly/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.the-arm.com/2008/06/anti-agile-words-weekly/</link>
	<description>A weblog about Methodologies for Development</description>
	<lastBuildDate>Mon, 14 Jun 2010 09:49:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: toni</title>
		<link>http://www.the-arm.com/2008/06/anti-agile-words-weekly/comment-page-1/#comment-11809</link>
		<dc:creator>toni</dc:creator>
		<pubDate>Tue, 26 Aug 2008 06:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.java2me.org/2008/06/20/anti-agile-words-weekly/#comment-11809</guid>
		<description>Oh daily is good, weekly is also good. 
I didn&#039;t had the time to reply the Sachin comment, there was something missing and unclear on my post. 

The anger on the weekly term was coming from an upfront planning, was coming from a request to plan to do every week something. Without a real understanding if it was needed or not. 

Weekly project checkpoints for example are necessary to feel the rhythm of the project and understand how is going, daily standups are something I can&#039;t imagine working without. 

Or let&#039;s remove standups too, let&#039;s try that, as an experiment, let&#039;s imagine working without standups, what will happen? What else can we use in the team to make everything working at the same way or even better?  
Can we improve the team performance removing standups?</description>
		<content:encoded><![CDATA[<p>Oh daily is good, weekly is also good.<br />
I didn&#8217;t had the time to reply the Sachin comment, there was something missing and unclear on my post. </p>
<p>The anger on the weekly term was coming from an upfront planning, was coming from a request to plan to do every week something. Without a real understanding if it was needed or not. </p>
<p>Weekly project checkpoints for example are necessary to feel the rhythm of the project and understand how is going, daily standups are something I can&#8217;t imagine working without. </p>
<p>Or let&#8217;s remove standups too, let&#8217;s try that, as an experiment, let&#8217;s imagine working without standups, what will happen? What else can we use in the team to make everything working at the same way or even better?<br />
Can we improve the team performance removing standups?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kris Kemper</title>
		<link>http://www.the-arm.com/2008/06/anti-agile-words-weekly/comment-page-1/#comment-11803</link>
		<dc:creator>Kris Kemper</dc:creator>
		<pubDate>Tue, 26 Aug 2008 04:27:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.java2me.org/2008/06/20/anti-agile-words-weekly/#comment-11803</guid>
		<description>What about a daily standup? Is weekly bad, but daily good?</description>
		<content:encoded><![CDATA[<p>What about a daily standup? Is weekly bad, but daily good?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sachin</title>
		<link>http://www.the-arm.com/2008/06/anti-agile-words-weekly/comment-page-1/#comment-10143</link>
		<dc:creator>Sachin</dc:creator>
		<pubDate>Fri, 20 Jun 2008 06:37:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.java2me.org/2008/06/20/anti-agile-words-weekly/#comment-10143</guid>
		<description>Well, I agree with you partially about how weekly sounds rigid. I always find myself in dilemma of missing a weekly meeting just because there is not enough content to discuss about. Sometimes, I find those meetings useful too because those are needed. Now here is my other perspective which I need to put on table to defend the term weekly:

- What if there are many business users involved in a meeting related to requirements? Doesn&#039;t a planned weekly meet help? On ad-hoc or need basis we might miss some of the users due to unavailability.

- Business users and people who are outside team needs to plan their calendars. How those people are going to mark their calendars or decide what is their weekly agenda?

For developers or people internal to the team (customer analysts etc. who are sitting with team), I don&#039;t find any issues because development and related meetings (stand-ups, huddles) are something which they can decide on their own as it doesn&#039;t affect the external participants. 

All I could suggest is, in the beginning of meeting just ask do you really want to carry out those meetings. 

Thats just me!</description>
		<content:encoded><![CDATA[<p>Well, I agree with you partially about how weekly sounds rigid. I always find myself in dilemma of missing a weekly meeting just because there is not enough content to discuss about. Sometimes, I find those meetings useful too because those are needed. Now here is my other perspective which I need to put on table to defend the term weekly:</p>
<p>- What if there are many business users involved in a meeting related to requirements? Doesn&#8217;t a planned weekly meet help? On ad-hoc or need basis we might miss some of the users due to unavailability.</p>
<p>- Business users and people who are outside team needs to plan their calendars. How those people are going to mark their calendars or decide what is their weekly agenda?</p>
<p>For developers or people internal to the team (customer analysts etc. who are sitting with team), I don&#8217;t find any issues because development and related meetings (stand-ups, huddles) are something which they can decide on their own as it doesn&#8217;t affect the external participants. </p>
<p>All I could suggest is, in the beginning of meeting just ask do you really want to carry out those meetings. </p>
<p>Thats just me!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
