<?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 Management And Feedback</title>
	<atom:link href="http://blog.softwareprojects.org/project-management-and-feedback-265.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html</link>
	<description>Projects Are About People. Awesome.</description>
	<lastBuildDate>Wed, 10 Mar 2010 20:27:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Cymberly</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-9699</link>
		<dc:creator>Cymberly</dc:creator>
		<pubDate>Mon, 02 Mar 2009 12:26:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-9699</guid>
		<description>Whenever I have a verbal communication, I usually follow up with the person via email saying, &quot;per our conversation...&quot; Then, I save the email for future reference. I avoid verbal communication as much a possible and if any direction is given, always try to document it in writing.</description>
		<content:encoded><![CDATA[<p>Whenever I have a verbal communication, I usually follow up with the person via email saying, &#8220;per our conversation&#8230;&#8221; Then, I save the email for future reference. I avoid verbal communication as much a possible and if any direction is given, always try to document it in writing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Future of Project Management Software: Easy Projects .NET &#124; Project Management Resources, Templates, Books, Tools, News :: PMToolbox</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-8027</link>
		<dc:creator>Future of Project Management Software: Easy Projects .NET &#124; Project Management Resources, Templates, Books, Tools, News :: PMToolbox</dc:creator>
		<pubDate>Tue, 09 Sep 2008 05:25:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-8027</guid>
		<description>[...] Proj&#173;e&#173;ct&#173; M&#173;a&#173;n&#173;a&#173;g&#173;e&#173;m&#173;e&#173;n&#173;t&#173; A&amp;#... A&#173;s&#173; a&#173; kid I pla&#173;yed th&#173;is&#173; little ga&#173;me a&#173;t s&#173;ch&#173;o&#173;o&#173;l we ca&#173;lled &#8216;teleph&#173;o&#173;n&#173;e lin&#173;e&#8217;. Twen&#173;ty kids&#173; were h&#173;urdled up&#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] Proj&#173;e&#173;ct&#173; M&#173;a&#173;n&#173;a&#173;g&#173;e&#173;m&#173;e&#173;n&#173;t&#173; A&amp;#&#8230; A&#173;s&#173; a&#173; kid I pla&#173;yed th&#173;is&#173; little ga&#173;me a&#173;t s&#173;ch&#173;o&#173;o&#173;l we ca&#173;lled &#8216;teleph&#173;o&#173;n&#173;e lin&#173;e&#8217;. Twen&#173;ty kids&#173; were h&#173;urdled up&#8230; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Create Resilience In Your Process By Following The Sun &#8212; Project Shrink</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-7862</link>
		<dc:creator>Create Resilience In Your Process By Following The Sun &#8212; Project Shrink</dc:creator>
		<pubDate>Thu, 28 Aug 2008 19:06:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-7862</guid>
		<description>[...] is one of the great enablers of resilience. If you can get feedback fast into your process, you can absorb changes like a vacuum [...]</description>
		<content:encoded><![CDATA[<p>[...] is one of the great enablers of resilience. If you can get feedback fast into your process, you can absorb changes like a vacuum [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-5367</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Fri, 06 Jun 2008 08:10:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-5367</guid>
		<description>Hi Myroslava, thanks for bringing that up. Yes, of course, one can record e.g. skype calls, or capture screen casts (online meetings). I wonder how many people actually do that... and what experiences are? So if anyone can share some experiences, highly appreciated.</description>
		<content:encoded><![CDATA[<p>Hi Myroslava, thanks for bringing that up. Yes, of course, one can record e.g. skype calls, or capture screen casts (online meetings). I wonder how many people actually do that&#8230; and what experiences are? So if anyone can share some experiences, highly appreciated.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Myroslava Symonenko</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-5351</link>
		<dc:creator>Myroslava Symonenko</dc:creator>
		<pubDate>Tue, 03 Jun 2008 15:09:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-5351</guid>
		<description>Speaking about the medium of the project communication: 1) verbal (distant verbal communication = audio conferences) communication can be logged and stored nowadays which is a plus if you need to come back to review the feedback later;
2) graphical information can also be passed with the help of desktop and/or application sharing, and as well logged and stored to the corresponding topic or task. On top of this a meeting participant can usually use an annotation tool to write the brief comments (which all the participants may see) on the screen. Of course for the extensive descriptions it&#039;s usually better to create a separate doc.</description>
		<content:encoded><![CDATA[<p>Speaking about the medium of the project communication: 1) verbal (distant verbal communication = audio conferences) communication can be logged and stored nowadays which is a plus if you need to come back to review the feedback later;<br />
2) graphical information can also be passed with the help of desktop and/or application sharing, and as well logged and stored to the corresponding topic or task. On top of this a meeting participant can usually use an annotation tool to write the brief comments (which all the participants may see) on the screen. Of course for the extensive descriptions it&#8217;s usually better to create a separate doc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-5327</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Mon, 02 Jun 2008 09:37:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-5327</guid>
		<description>Thanks Ali for the comment. I entirely agree.</description>
		<content:encoded><![CDATA[<p>Thanks Ali for the comment. I entirely agree.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ali Anani</title>
		<link>http://blog.softwareprojects.org/project-management-and-feedback-265.html/comment-page-1#comment-5312</link>
		<dc:creator>Ali Anani</dc:creator>
		<pubDate>Sat, 31 May 2008 05:43:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=265#comment-5312</guid>
		<description>The time factor is important in feedback. Feedback has a purpose to help managers to adapt to new realities with resilience. Slow motion feedback might lead to lagging adjustments and feedbacks are this way useless or might lead to incorrect adaptation. So, verbal feedback might be useful in reducing time frames. I concur with the need to verify information to ensure its correctness. Adaptation to wrong information might only lead to undesirable outcomes.</description>
		<content:encoded><![CDATA[<p>The time factor is important in feedback. Feedback has a purpose to help managers to adapt to new realities with resilience. Slow motion feedback might lead to lagging adjustments and feedbacks are this way useless or might lead to incorrect adaptation. So, verbal feedback might be useful in reducing time frames. I concur with the need to verify information to ensure its correctness. Adaptation to wrong information might only lead to undesirable outcomes.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
