<?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: Visualizing Your Project Meetings</title>
	<atom:link href="http://www.pmhut.com/visualizing-your-project-meetings/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/visualizing-your-project-meetings</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 19:59:49 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Atul</title>
		<link>http://www.pmhut.com/visualizing-your-project-meetings/comment-page-1#comment-17520</link>
		<dc:creator>Atul</dc:creator>
		<pubDate>Mon, 22 Feb 2010 10:29:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4834#comment-17520</guid>
		<description>Hi Olesya, 

Thanks for the excellent points regarding meetings. I would like to add two things.

One is to track all open TODOs of past meetings to completion. This can be done in every instance of recurring meetings. For completed tasks, the TODOs can me marked as closed. For incomplete tasks, it should be kept OPEN and a new expected closure date should be set, so that it is tracked in a later instance of the meeting.

Second is to use a software tool to write the 'Minutes of Meeting' *during* the meeting, so that the captured minutes are comprehensive, accurate and short ! They should be circulated right after the meeting.

You may want to evalute a free and open source tool for the same, called YaMA. Checkout http://yama.sourceforge.net.

Regards,
-- Atul</description>
		<content:encoded><![CDATA[<p>Hi Olesya, </p>
<p>Thanks for the excellent points regarding meetings. I would like to add two things.</p>
<p>One is to track all open TODOs of past meetings to completion. This can be done in every instance of recurring meetings. For completed tasks, the TODOs can me marked as closed. For incomplete tasks, it should be kept OPEN and a new expected closure date should be set, so that it is tracked in a later instance of the meeting.</p>
<p>Second is to use a software tool to write the &#8216;Minutes of Meeting&#8217; *during* the meeting, so that the captured minutes are comprehensive, accurate and short ! They should be circulated right after the meeting.</p>
<p>You may want to evalute a free and open source tool for the same, called YaMA. Checkout <a href="http://yama.sourceforge.net" rel="nofollow">http://yama.sourceforge.net</a>.</p>
<p>Regards,<br />
&#8211; Atul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Francis Norman</title>
		<link>http://www.pmhut.com/visualizing-your-project-meetings/comment-page-1#comment-17436</link>
		<dc:creator>Francis Norman</dc:creator>
		<pubDate>Sun, 21 Feb 2010 07:35:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4834#comment-17436</guid>
		<description>Interesting article Olesya, some very good points around meetings.  In my experience, the features of good meetings are, a published agenda for everyone beforehand, only invite those who need to be there, a strong leader for the meeting who will keep the discussion on topic and engage everyone in discussions, not just the usual few who love to talk, keep the meeting on schedule and publish the minutes promptly after the meeting.  Also, meetings can have "expiry dates", it is good to review the ROI of meetings periodically to ensure they are still required.</description>
		<content:encoded><![CDATA[<p>Interesting article Olesya, some very good points around meetings.  In my experience, the features of good meetings are, a published agenda for everyone beforehand, only invite those who need to be there, a strong leader for the meeting who will keep the discussion on topic and engage everyone in discussions, not just the usual few who love to talk, keep the meeting on schedule and publish the minutes promptly after the meeting.  Also, meetings can have &#8220;expiry dates&#8221;, it is good to review the ROI of meetings periodically to ensure they are still required.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

