<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments for Project Management Roundtable</title>
	<atom:link href="http://blogs.capella.edu/projectmanagementroundtable/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.capella.edu/projectmanagementroundtable</link>
	<description>A Community for Project Management Research and Practice</description>
	<lastBuildDate>Wed, 17 Feb 2010 16:48:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Over Thinking the Project? by Dr. Loran Walker</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2010/02/01/over-thinking-the-project/comment-page-1/#comment-123</link>
		<dc:creator>Dr. Loran Walker</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:48:58 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=306#comment-123</guid>
		<description>Yes, I agree that too much detail or agonizing over a project plan can prove to be counter productive.  It is the age old problem of &quot;Analysis Paralysis&quot;!  In regard to team members or stakeholders losing focus, this is where one should have an agenda and a time limit on weekly or team meetings.  

I know of one organization where they do not sit down but gather in a circle and pass around an item and when you have the item it is your turn to speak and/or ask questions.  The strategy is to get the information out so that the team can move on with the day&#039;s work.

I have been in organizations where the weekly meeting was a &quot;must have&quot; even if there was nothing on the agenda!  To me a meeting needs to happen when there is something to talk about that is impeding the progress of the project or there needs to be clarifications made or coordination of efforts.</description>
		<content:encoded><![CDATA[<p>Yes, I agree that too much detail or agonizing over a project plan can prove to be counter productive.  It is the age old problem of &#8220;Analysis Paralysis&#8221;!  In regard to team members or stakeholders losing focus, this is where one should have an agenda and a time limit on weekly or team meetings.  </p>
<p>I know of one organization where they do not sit down but gather in a circle and pass around an item and when you have the item it is your turn to speak and/or ask questions.  The strategy is to get the information out so that the team can move on with the day&#8217;s work.</p>
<p>I have been in organizations where the weekly meeting was a &#8220;must have&#8221; even if there was nothing on the agenda!  To me a meeting needs to happen when there is something to talk about that is impeding the progress of the project or there needs to be clarifications made or coordination of efforts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Over Thinking the Project? by Stan Emelander</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2010/02/01/over-thinking-the-project/comment-page-1/#comment-122</link>
		<dc:creator>Stan Emelander</dc:creator>
		<pubDate>Wed, 17 Feb 2010 16:26:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=306#comment-122</guid>
		<description>I walk the line between too much and not enough analysis fairly often.  Many times in meetings I carry out internal what-if discussions, trying to sort out my own perspective.  I have to be careful about speaking out loud in these circumstances.  If there are more than two variables to consider at one time for a specific topic, I lose half the team members if I to mash things together too quickly.  It is like the process of “chunking” – if you are familiar with concepts you can cover a lot of ground.  If not, you have to take your time.  Also, if I push for too much detail coming out of single meeting, people can get tired or confused, lowering our overall effectiveness.

A variation on this topic:  I do encounter managers that plan to [seems to me] unnecessary to detail for certain events.  An example is stage-gate reviews that become highly choreographed affairs planned to excruciating detail.  Some reviews are “staged” rather than “stage” meetings.  There is no avoiding some charts and tables to display performance information, but I prefer discussion-centered meetings to power point-centered shows.</description>
		<content:encoded><![CDATA[<p>I walk the line between too much and not enough analysis fairly often.  Many times in meetings I carry out internal what-if discussions, trying to sort out my own perspective.  I have to be careful about speaking out loud in these circumstances.  If there are more than two variables to consider at one time for a specific topic, I lose half the team members if I to mash things together too quickly.  It is like the process of “chunking” – if you are familiar with concepts you can cover a lot of ground.  If not, you have to take your time.  Also, if I push for too much detail coming out of single meeting, people can get tired or confused, lowering our overall effectiveness.</p>
<p>A variation on this topic:  I do encounter managers that plan to [seems to me] unnecessary to detail for certain events.  An example is stage-gate reviews that become highly choreographed affairs planned to excruciating detail.  Some reviews are “staged” rather than “stage” meetings.  There is no avoiding some charts and tables to display performance information, but I prefer discussion-centered meetings to power point-centered shows.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Troublesome Team Member by Dr. Loran Walker</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/11/23/the-troublesome-team-member/comment-page-1/#comment-121</link>
		<dc:creator>Dr. Loran Walker</dc:creator>
		<pubDate>Tue, 16 Feb 2010 19:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=278#comment-121</guid>
		<description>Excellent insights!  I agree that the final action may be to remove the disruptive person so the project may move forward.  However, that action may have to be acted upon sooner, especially if the team&#039;s performance is suffering.

Another idea may be to intervene with the person with peers or a management team emphasizing that the success of the project is everyone&#039;s concern and from that common ground move forward.

Timing and patience is everything in these types of situations...</description>
		<content:encoded><![CDATA[<p>Excellent insights!  I agree that the final action may be to remove the disruptive person so the project may move forward.  However, that action may have to be acted upon sooner, especially if the team&#8217;s performance is suffering.</p>
<p>Another idea may be to intervene with the person with peers or a management team emphasizing that the success of the project is everyone&#8217;s concern and from that common ground move forward.</p>
<p>Timing and patience is everything in these types of situations&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Troublesome Team Member by Stan Emelander</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/11/23/the-troublesome-team-member/comment-page-1/#comment-120</link>
		<dc:creator>Stan Emelander</dc:creator>
		<pubDate>Mon, 15 Feb 2010 17:52:56 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=278#comment-120</guid>
		<description>I am encouraged that newhere has determined a leadership philosophy to follow.  That is a good start.  I prefer the transactional/transformational model.  Using this perspective, laissez faire leadership, only intervening when there is a problem is not an option, as Dr. Walker commented.  That leaves you with active transaction and transformation.  If you do not have any rewards to offer, transaction is out of the picture, leaving transformation.  Transformation involves sharing your goals and vision for the project in a manner that is attractive.  It focuses on goals, what can be accomplished, rather than negatives. 

It seems newhere could rightly say that he/she does not understand what troublesome’s goals are.   If troublesome’s goal is project success, then there is a basis for moving ahead.  If it is centered on fighting the organization’s methodology, then there is a problem.  Whether the disagreement is cognitive (issues based) or affective (personality based) can be important as well.  The situation reads as if cognitive conflict is bleeding over to affective problems, affecting the team.  Whether PM is a bona-fide profession is beside the point – the organization is using PM methods, and following standards (benchmarks) is important.  

We all like to be able to handle problems and risks with our own resources, but in dealing with a disruptive peer I think that presenting the situation to higher-level managers is good option.   My experience has been that the downsides from removal are less than trying to accommodate a disruptive person.</description>
		<content:encoded><![CDATA[<p>I am encouraged that newhere has determined a leadership philosophy to follow.  That is a good start.  I prefer the transactional/transformational model.  Using this perspective, laissez faire leadership, only intervening when there is a problem is not an option, as Dr. Walker commented.  That leaves you with active transaction and transformation.  If you do not have any rewards to offer, transaction is out of the picture, leaving transformation.  Transformation involves sharing your goals and vision for the project in a manner that is attractive.  It focuses on goals, what can be accomplished, rather than negatives. </p>
<p>It seems newhere could rightly say that he/she does not understand what troublesome’s goals are.   If troublesome’s goal is project success, then there is a basis for moving ahead.  If it is centered on fighting the organization’s methodology, then there is a problem.  Whether the disagreement is cognitive (issues based) or affective (personality based) can be important as well.  The situation reads as if cognitive conflict is bleeding over to affective problems, affecting the team.  Whether PM is a bona-fide profession is beside the point – the organization is using PM methods, and following standards (benchmarks) is important.  </p>
<p>We all like to be able to handle problems and risks with our own resources, but in dealing with a disruptive peer I think that presenting the situation to higher-level managers is good option.   My experience has been that the downsides from removal are less than trying to accommodate a disruptive person.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Troublesome Team Member by Dr. Loran Walker</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/11/23/the-troublesome-team-member/comment-page-1/#comment-100</link>
		<dc:creator>Dr. Loran Walker</dc:creator>
		<pubDate>Sun, 24 Jan 2010 15:33:18 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=278#comment-100</guid>
		<description>There are different ways of approach an employee in this type of scenario.  This is only my opinion based on what you&#039;ve said but I would simple confront the person with the idea that mutual respect is needed in order for any conversation to take place.

The three approaches can be avoidance of the issue, smoothing over the issue or confronting the issue.  In this case the first two do not seem to be a good choice. 

What I have seen in other scenarios is the person who is creating the issues is removed from the team in order for the project to move forward.

-- Loran</description>
		<content:encoded><![CDATA[<p>There are different ways of approach an employee in this type of scenario.  This is only my opinion based on what you&#8217;ve said but I would simple confront the person with the idea that mutual respect is needed in order for any conversation to take place.</p>
<p>The three approaches can be avoidance of the issue, smoothing over the issue or confronting the issue.  In this case the first two do not seem to be a good choice. </p>
<p>What I have seen in other scenarios is the person who is creating the issues is removed from the team in order for the project to move forward.</p>
<p>&#8211; Loran</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Free: Live Career Webinars by Nona Haller</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/08/16/free-live-career-webinars/comment-page-1/#comment-95</link>
		<dc:creator>Nona Haller</dc:creator>
		<pubDate>Wed, 16 Dec 2009 14:02:42 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=205#comment-95</guid>
		<description>You are quite welcome, Glen.  I hope you find the webinars helpful!

Nona</description>
		<content:encoded><![CDATA[<p>You are quite welcome, Glen.  I hope you find the webinars helpful!</p>
<p>Nona</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Free: Live Career Webinars by Glen Givens</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/08/16/free-live-career-webinars/comment-page-1/#comment-94</link>
		<dc:creator>Glen Givens</dc:creator>
		<pubDate>Mon, 14 Dec 2009 22:03:59 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=205#comment-94</guid>
		<description>Thank you Nona for the advance notice of these Career Webinars. I have signed up and have received confirmation to be able to take advantage of this participation. Every little bit helps.

Glen Givens</description>
		<content:encoded><![CDATA[<p>Thank you Nona for the advance notice of these Career Webinars. I have signed up and have received confirmation to be able to take advantage of this participation. Every little bit helps.</p>
<p>Glen Givens</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Troublesome Team Member by newhere</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/11/23/the-troublesome-team-member/comment-page-1/#comment-88</link>
		<dc:creator>newhere</dc:creator>
		<pubDate>Thu, 03 Dec 2009 01:12:11 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=278#comment-88</guid>
		<description>GREAT question.
I am dealing with a troublesome team member that is a very experienced SME (with no pmp training or understanding) who has been assigned a leadership role on a project that interacts with mine.  The team is pushing back on working with him and I&#039;m starting to avoid his calls too, since we usually spend considerable amounts of time arguing about whether or not project management is a &quot;real&quot; discipline, or addressing the person&#039;s many technical issues using the tools established by the PMO.  

My plan has been to use the situational leadership approach to separate the root cause of the issues (ability vs. willingness).  Next I need to describe the issue to him in these terms and ask some questions to verify, then address the gap by suggesting the agreement I need to get.  If issues continue, they need to be addressed immediately and with an appropriately grave approach (referring to the previous conversation and agreements not being kept, being honest but tactful about how specifically the behaviour is an obstacle to the project, documenting the conversation, and discussing before and after with my own supervisor and/or the sponsor).  

If the problem persists beyond that, then I will raise the situation further with the sponsor and my director as a significant obstacle to the success of the project, summarize the risks of allowing the situation to continue, and discuss the options for intervention or corrective action.  From there, it is their call.  I will continue to be firm in any agreements we have made about our communication, such as time limits on unscheduled phone conversations, or transferring an argument to the issue log for future resolution when it&#039;s obvious we&#039;re not making progress.  

Any ideas/issues/feedback?  I&#039;ve just spent some time thinking about it and sometimes writing it out like this helps me clarify :)  The main issue I see arising is that the person doesn&#039;t seem to have any respect for the discipline of project managementm which bothers me and I get sidetracked into conversations about why pm is important rather than sticking to the real issue.  How do I keep it on track when the blustering, egotistical, condescending comments start flying at me?</description>
		<content:encoded><![CDATA[<p>GREAT question.<br />
I am dealing with a troublesome team member that is a very experienced SME (with no pmp training or understanding) who has been assigned a leadership role on a project that interacts with mine.  The team is pushing back on working with him and I&#8217;m starting to avoid his calls too, since we usually spend considerable amounts of time arguing about whether or not project management is a &#8220;real&#8221; discipline, or addressing the person&#8217;s many technical issues using the tools established by the PMO.  </p>
<p>My plan has been to use the situational leadership approach to separate the root cause of the issues (ability vs. willingness).  Next I need to describe the issue to him in these terms and ask some questions to verify, then address the gap by suggesting the agreement I need to get.  If issues continue, they need to be addressed immediately and with an appropriately grave approach (referring to the previous conversation and agreements not being kept, being honest but tactful about how specifically the behaviour is an obstacle to the project, documenting the conversation, and discussing before and after with my own supervisor and/or the sponsor).  </p>
<p>If the problem persists beyond that, then I will raise the situation further with the sponsor and my director as a significant obstacle to the success of the project, summarize the risks of allowing the situation to continue, and discuss the options for intervention or corrective action.  From there, it is their call.  I will continue to be firm in any agreements we have made about our communication, such as time limits on unscheduled phone conversations, or transferring an argument to the issue log for future resolution when it&#8217;s obvious we&#8217;re not making progress.  </p>
<p>Any ideas/issues/feedback?  I&#8217;ve just spent some time thinking about it and sometimes writing it out like this helps me clarify <img src='http://blogs.capella.edu/projectmanagementroundtable/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' />   The main issue I see arising is that the person doesn&#8217;t seem to have any respect for the discipline of project managementm which bothers me and I get sidetracked into conversations about why pm is important rather than sticking to the real issue.  How do I keep it on track when the blustering, egotistical, condescending comments start flying at me?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on New Doctoral Research Grants – Application Deadline October 30, 2009 by My-Project-Management-Expert.com</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/10/28/new-doctoral-research-grants-program-%e2%80%93-application-deadline-october-30-2009/comment-page-1/#comment-83</link>
		<dc:creator>My-Project-Management-Expert.com</dc:creator>
		<pubDate>Thu, 29 Oct 2009 11:15:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=260#comment-83</guid>
		<description>As far as I am concerned global project management needs to deal with &lt;a href=&quot;http://www.my-project-management-expert.com/managing-project-teams.html&quot; rel=&quot;nofollow&quot;&gt;managing project teams&lt;/a&gt; and also have a huge emphasis on &lt;a href=&quot;http://www.my-project-management-expert.com/project-communications-management.html&quot; rel=&quot;nofollow&quot;&gt;project communications management&lt;/a&gt;.

The reason being that as someone who has managed numerous global programs the key difficulties I&#039;ve encountered are dealing with remote / offhore teams and effectively communicating with teams who&#039;s grasp of English is not as good as they might like to think.

Regards

Susan de Sousa
Site Editor http://www.my-project-management-expert.com</description>
		<content:encoded><![CDATA[<p>As far as I am concerned global project management needs to deal with <a href="http://www.my-project-management-expert.com/managing-project-teams.html" rel="nofollow">managing project teams</a> and also have a huge emphasis on <a href="http://www.my-project-management-expert.com/project-communications-management.html" rel="nofollow">project communications management</a>.</p>
<p>The reason being that as someone who has managed numerous global programs the key difficulties I&#8217;ve encountered are dealing with remote / offhore teams and effectively communicating with teams who&#8217;s grasp of English is not as good as they might like to think.</p>
<p>Regards</p>
<p>Susan de Sousa<br />
Site Editor <a href="http://www.my-project-management-expert.com" rel="nofollow">http://www.my-project-management-expert.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Improving Your Group Presentation Skills by Dr. Loran Walker</title>
		<link>http://blogs.capella.edu/projectmanagementroundtable/2009/10/05/improving-your-group-presentation-skills/comment-page-1/#comment-82</link>
		<dc:creator>Dr. Loran Walker</dc:creator>
		<pubDate>Mon, 26 Oct 2009 16:15:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.capella.edu/projectmanagementroundtable/?p=248#comment-82</guid>
		<description>Seth, appreciate the comment!

Are there other organizations or ways to improve group presentation skills?</description>
		<content:encoded><![CDATA[<p>Seth, appreciate the comment!</p>
<p>Are there other organizations or ways to improve group presentation skills?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
