<?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: Everyday Status Meeting &#8211; An Absolute Project Killer</title>
	<atom:link href="http://utpal.net/blog/everyday-status-meeting-an-absolute-project-killer/feed/" rel="self" type="application/rss+xml" />
	<link>http://utpal.net/blog/everyday-status-meeting-an-absolute-project-killer/</link>
	<description></description>
	<lastBuildDate>Mon, 16 Apr 2012 18:21:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Utpal Vaishnav</title>
		<link>http://utpal.net/blog/everyday-status-meeting-an-absolute-project-killer/comment-page-1/#comment-360</link>
		<dc:creator>Utpal Vaishnav</dc:creator>
		<pubDate>Thu, 10 Sep 2009 11:27:11 +0000</pubDate>
		<guid isPermaLink="false">http://utpal.net/blog/?p=581#comment-360</guid>
		<description>Hi Maulik,

Thanks for stopping by and commenting. I understand totally what you expressed in your comments.

How true is the old saying, &quot;Failing to plan means planning to fail&quot; in such situations!

Best,
Utpal</description>
		<content:encoded><![CDATA[<p>Hi Maulik,</p>
<p>Thanks for stopping by and commenting. I understand totally what you expressed in your comments.</p>
<p>How true is the old saying, &#8220;Failing to plan means planning to fail&#8221; in such situations!</p>
<p>Best,<br />
Utpal</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Maulik shah</title>
		<link>http://utpal.net/blog/everyday-status-meeting-an-absolute-project-killer/comment-page-1/#comment-359</link>
		<dc:creator>Maulik shah</dc:creator>
		<pubDate>Thu, 10 Sep 2009 11:19:28 +0000</pubDate>
		<guid isPermaLink="false">http://utpal.net/blog/?p=581#comment-359</guid>
		<description>Simply great.

Totally agree with you.

Team members are always interested to know what other team members are doing at the initial stage of the project, but when it becomes routine its boring and all are only waiting to finish their turn or meeting.

Certain options to avoid:
1)We should use agile Scrum method.
2)We should plan meeting agenda and discussion points (Email all team members that i want to discuss on following points and all) and give specific time slot to each team member which will reduce unnecessary involvement of all.We can define certain period for which all have to available for the meeting.</description>
		<content:encoded><![CDATA[<p>Simply great.</p>
<p>Totally agree with you.</p>
<p>Team members are always interested to know what other team members are doing at the initial stage of the project, but when it becomes routine its boring and all are only waiting to finish their turn or meeting.</p>
<p>Certain options to avoid:<br />
1)We should use agile Scrum method.<br />
2)We should plan meeting agenda and discussion points (Email all team members that i want to discuss on following points and all) and give specific time slot to each team member which will reduce unnecessary involvement of all.We can define certain period for which all have to available for the meeting.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

