<?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: Communication in (Not Only) Project Management</title>
	<atom:link href="http://blog.brodzinski.com/2008/10/communication-in-not-only-project.html/feed" rel="self" type="application/rss+xml" />
	<link>http://blog.brodzinski.com/2008/10/communication-in-not-only-project.html</link>
	<description>Dealing with software projects in real life</description>
	<lastBuildDate>Fri, 10 Feb 2012 19:07:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: yatsevsky</title>
		<link>http://blog.brodzinski.com/2008/10/communication-in-not-only-project.html#comment-2039</link>
		<dc:creator>yatsevsky</dc:creator>
		<pubDate>Tue, 21 Oct 2008 19:13:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2008/10/communication-in-not-only-project-management.html#comment-2039</guid>
		<description>I had a case of failing project just because the stakeholder had no time to communicate over ambigious points, nor had time to review demos. After formal release, the project appeared to be skipping some of the most vital requirements which are actually weren&#039;t recorded from the very beginning (nothing to refer, still client&#039;s thinking he&#039;s right).&lt;br/&gt;&lt;br/&gt;Lesson&#039;s learned. Stakeholders should be always aware they need to contribute to project as well, no matter which methodology is chosen still.</description>
		<content:encoded><![CDATA[<p>I had a case of failing project just because the stakeholder had no time to communicate over ambigious points, nor had time to review demos. After formal release, the project appeared to be skipping some of the most vital requirements which are actually weren&#8217;t recorded from the very beginning (nothing to refer, still client&#8217;s thinking he&#8217;s right).</p>
<p>Lesson&#8217;s learned. Stakeholders should be always aware they need to contribute to project as well, no matter which methodology is chosen still.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pawel Brodzinski</title>
		<link>http://blog.brodzinski.com/2008/10/communication-in-not-only-project.html#comment-2038</link>
		<dc:creator>Pawel Brodzinski</dc:creator>
		<pubDate>Tue, 07 Oct 2008 12:58:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2008/10/communication-in-not-only-project-management.html#comment-2038</guid>
		<description>I wouldn&#039;t go that far. Yes, delivering clear feedback is crucial to improve communication. However, I definitely wouldn&#039;t treat establishing feedback methdology as a sure-shot technique. Most likely it is needed in environments which includes big number of people from different countries and different cultures, but if you&#039;re dealing with small team and (almost) everyone works in the same place there are much better techniques to achieve the goal.</description>
		<content:encoded><![CDATA[<p>I wouldn&#8217;t go that far. Yes, delivering clear feedback is crucial to improve communication. However, I definitely wouldn&#8217;t treat establishing feedback methdology as a sure-shot technique. Most likely it is needed in environments which includes big number of people from different countries and different cultures, but if you&#8217;re dealing with small team and (almost) everyone works in the same place there are much better techniques to achieve the goal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ExecutiveBrief</title>
		<link>http://blog.brodzinski.com/2008/10/communication-in-not-only-project.html#comment-2037</link>
		<dc:creator>ExecutiveBrief</dc:creator>
		<pubDate>Tue, 07 Oct 2008 12:29:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.brodzinski.com/2008/10/communication-in-not-only-project-management.html#comment-2037</guid>
		<description>In project management, feedback is an important element of communication, and as communication is vital to business success, feedback is therefore a key contributor to success as well.&lt;br/&gt; &lt;br/&gt;One of the main catalysts for failure or difficulty within the team is misunderstandings in communication. Business environment inherently brings together team members with different communication styles, language, and many other factors that may lead to differences in interpreting communication or verbal and non-verbal cues. Ideally, before a team is established, a feedback methodology should be discussed in order to avoid any future miscommunications that may potentially serve to railroad project efforts. &lt;br/&gt;&lt;br/&gt;When the feedback process is carried out appropriately, there are many benefits to be realized. Feedback is a valuable tool in building employee confidence, boosting morale, and enhancing the reputation of the business. &lt;br/&gt;&lt;br/&gt;Businesses must understand the importance of customer feedback and consider how valuable this information can be as they work to create new or revise existing services and solutions. In addition, staff training should be offered so that employees are capable of giving and receiving feedback in such a way that facilitates and encourages discussion and further development of both the staff and the company as a whole. &lt;br/&gt;&lt;br/&gt;&lt;a HREF=&quot;http://www.executivebrief.com/article/exploiting-feedback-to-improve-bottom-line-performance&quot; REL=&quot;nofollow&quot;&gt; http://www.executivebrief.com/article/exploiting-feedback-to-improve-bottom-line-performance&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>In project management, feedback is an important element of communication, and as communication is vital to business success, feedback is therefore a key contributor to success as well.</p>
<p>One of the main catalysts for failure or difficulty within the team is misunderstandings in communication. Business environment inherently brings together team members with different communication styles, language, and many other factors that may lead to differences in interpreting communication or verbal and non-verbal cues. Ideally, before a team is established, a feedback methodology should be discussed in order to avoid any future miscommunications that may potentially serve to railroad project efforts. </p>
<p>When the feedback process is carried out appropriately, there are many benefits to be realized. Feedback is a valuable tool in building employee confidence, boosting morale, and enhancing the reputation of the business. </p>
<p>Businesses must understand the importance of customer feedback and consider how valuable this information can be as they work to create new or revise existing services and solutions. In addition, staff training should be offered so that employees are capable of giving and receiving feedback in such a way that facilitates and encourages discussion and further development of both the staff and the company as a whole. </p>
<p><a HREF="http://www.executivebrief.com/article/exploiting-feedback-to-improve-bottom-line-performance" REL="nofollow"> </a><a href="http://www.executivebrief.com/article/exploiting-feedback-to-improve-bottom-line-performance" rel="nofollow">http://www.executivebrief.com/article/exploiting-feedback-to-improve-bottom-line-performance</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

