<?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 Issue Log</title>
	<atom:link href="http://www.pmhut.com/project-issue-log/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/project-issue-log</link>
	<description></description>
	<pubDate>Sat, 11 Feb 2012 02:56:58 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Primoz Frelih, PMP</title>
		<link>http://www.pmhut.com/project-issue-log/comment-page-1#comment-8946</link>
		<dc:creator>Primoz Frelih, PMP</dc:creator>
		<pubDate>Wed, 09 Sep 2009 06:56:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3706#comment-8946</guid>
		<description>Thanks for bringing up the question about the issue log structure. In addition I would agree with Shawn's remark - to make each issue a potential action item. The OGC's log seems static and I guess it is a result of issue identification activities. In order to minimize project's issues there have to be some action and responsibility.</description>
		<content:encoded><![CDATA[<p>Thanks for bringing up the question about the issue log structure. In addition I would agree with Shawn&#8217;s remark - to make each issue a potential action item. The OGC&#8217;s log seems static and I guess it is a result of issue identification activities. In order to minimize project&#8217;s issues there have to be some action and responsibility.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Kelly</title>
		<link>http://www.pmhut.com/project-issue-log/comment-page-1#comment-8943</link>
		<dc:creator>Shawn Kelly</dc:creator>
		<pubDate>Wed, 09 Sep 2009 01:45:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=3706#comment-8943</guid>
		<description>I find the following additional fields to be invaluable within an issue log:

Owner – someone needs to be accountable for each issue; it probably is not the author

Target Date – Without a goal, the issue can not be managed appropriately

Priority – Not all issues are created equal

Peer Reviewer – builds consensus and increases communication when dysfunction exists (Be careful with this one. There is a lot of overhead in its use. Good during project recovery though)

Peer Review Target Date – see target date above</description>
		<content:encoded><![CDATA[<p>I find the following additional fields to be invaluable within an issue log:</p>
<p>Owner – someone needs to be accountable for each issue; it probably is not the author</p>
<p>Target Date – Without a goal, the issue can not be managed appropriately</p>
<p>Priority – Not all issues are created equal</p>
<p>Peer Reviewer – builds consensus and increases communication when dysfunction exists (Be careful with this one. There is a lot of overhead in its use. Good during project recovery though)</p>
<p>Peer Review Target Date – see target date above</p>
]]></content:encoded>
	</item>
</channel>
</rss>

