﻿<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Virtual Project Communications: Recent Comments</title><link>http://blog.virtualprojectcommunications.com</link><description /><generator>Quick Blog</generator><lastBuildDate>Tue, 13 May 2008 09:56:14 GMT</lastBuildDate><item><title>Comment on Project Communications Strategy</title><link>http://blog.virtualprojectcommunications.com/2007/06/13/project-communications-strategy.aspx#comment-563370</link><dc:creator>Audrey Kunkel</dc:creator><description>This is great! I'm working on some IT/engineering project communications plans for GE Infrastructure. These guidelines are going to be a huge help to me. &lt;BR&gt; &lt;BR&gt;Thank you!</description><guid isPermaLink="true">http://blog.virtualprojectcommunications.com/2007/06/13/project-communications-strategy.aspx#comment-563370</guid><pubDate>Wed, 26 Sep 2007 10:29:13 GMT</pubDate></item><item><title>Comment on Identify Stakeholder Readiness for Change</title><link>http://blog.virtualprojectcommunications.com/2007/06/21/identify-stakeholder-readiness-for-change.aspx#comment-554276</link><dc:creator>Jim Carras</dc:creator><description>True the Project Kickoff Meeting is an important single event within the project timeline.  Having the meeting demands getting ready for the meeting.  This would require a stakeholder analysis with a gap at least for the primary stakeholders.  From this you can better prepare for the content of the Kickoff Meeting to match their needs.  Just describing what the project is going to do, you stand the chance of missing the motives of the stakeholders and instead of getting them on-board early, you could create a barrier between the project and critical players.</description><guid isPermaLink="true">http://blog.virtualprojectcommunications.com/2007/06/21/identify-stakeholder-readiness-for-change.aspx#comment-554276</guid><pubDate>Thu, 20 Sep 2007 07:30:31 GMT</pubDate></item><item><title>Comment on Identify Stakeholder Readiness for Change</title><link>http://blog.virtualprojectcommunications.com/2007/06/21/identify-stakeholder-readiness-for-change.aspx#comment-416089</link><dc:creator>R C Goyal</dc:creator><description>The most important opportunity to communicate with the stakeholders is the 'Project Kickoff Meeting' to inform and appraise them on the project environment &amp;amp; seek their support clearly stating when, where, how they could make their valuable contribution leading to success in achieving the desired project goals.&lt;br /&gt; &lt;br /&gt;Project Manager must recognize that each functionary in the organization is an important stakeholder in his project &amp;amp; can extend their support at crucial time once they realize their importance. &lt;br /&gt; &lt;br /&gt;Stakeholders are not only the senior management personnel but also from HR, accounts, Administration, Facility Management (HW/SW &amp;amp; Network system administration)and travel-department. &lt;br /&gt; &lt;br /&gt;Inviting them in the 'Project Kickoff Meeting' itself makes them feel important. Important is that Project Manager in his briefing about the project scope, goal, schedule &amp;amp; constraints/assumptions includes clear mention about the role of each stakeholder invited in the meeting and seek their understanding &amp;amp; support.&lt;br /&gt; &lt;br /&gt;Project Kickoff Meeting is the most important and the earliest opportunity to present to the management his perception of the project schedule, budget &amp;amp; seek the funding and approval for the desired resources of all the kind/type.</description><guid isPermaLink="true">http://blog.virtualprojectcommunications.com/2007/06/21/identify-stakeholder-readiness-for-change.aspx#comment-416089</guid><pubDate>Sun, 01 Jul 2007 16:57:34 GMT</pubDate></item><item><title>Comment on Project Communications Strategy</title><link>http://blog.virtualprojectcommunications.com/2007/06/13/project-communications-strategy.aspx#comment-404779</link><dc:creator>Bob B</dc:creator><description>This is very interesting.  Many of the projects I have been assigned are too small to have any formal communications strategy, but I should have spent more time thinking through the different components you mentiond to see which are in fact critical to the project.  This is a good check-list to use.</description><guid isPermaLink="true">http://blog.virtualprojectcommunications.com/2007/06/13/project-communications-strategy.aspx#comment-404779</guid><pubDate>Mon, 25 Jun 2007 09:33:33 GMT</pubDate></item></channel></rss>