<?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: 10 Questions that Determine a Project&#8217;s Success</title>
	<atom:link href="http://www.pmhut.com/10-questions-that-determine-a-projects-success/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/10-questions-that-determine-a-projects-success</link>
	<description></description>
	<pubDate>Thu, 17 May 2012 02:24:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Laura Bamberg</title>
		<link>http://www.pmhut.com/10-questions-that-determine-a-projects-success/comment-page-1#comment-16168</link>
		<dc:creator>Laura Bamberg</dc:creator>
		<pubDate>Fri, 29 Jan 2010 16:14:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4690#comment-16168</guid>
		<description>Paul, you hit the nail on the head with the "who is the sponsor" question. Bad communication skills, even if you know who it is, can lead to just as many problems.http://www.steelray.com/blog/?p=8 addresses this in part.</description>
		<content:encoded><![CDATA[<p>Paul, you hit the nail on the head with the &#8220;who is the sponsor&#8221; question. Bad communication skills, even if you know who it is, can lead to just as many problems.http://www.steelray.com/blog/?p=8 addresses this in part.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://www.pmhut.com/10-questions-that-determine-a-projects-success/comment-page-1#comment-16127</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Thu, 28 Jan 2010 21:47:13 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4690#comment-16127</guid>
		<description>I like the "What does done look like" in Steven's comment. The definition of "done" should be communicated to everyone, from the stakeholders (on a broader scale) to team members (for the simplest of tasks).

Balanced Scorecards are a great idea Ross.</description>
		<content:encoded><![CDATA[<p>I like the &#8220;What does done look like&#8221; in Steven&#8217;s comment. The definition of &#8220;done&#8221; should be communicated to everyone, from the stakeholders (on a broader scale) to team members (for the simplest of tasks).</p>
<p>Balanced Scorecards are a great idea Ross.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ross Holman</title>
		<link>http://www.pmhut.com/10-questions-that-determine-a-projects-success/comment-page-1#comment-16126</link>
		<dc:creator>Ross Holman</dc:creator>
		<pubDate>Thu, 28 Jan 2010 21:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4690#comment-16126</guid>
		<description>I agree with Steven in that these are questions to be answered before a project begins.  A 'balanced scorecard' that is focused on the project's stakeholders determines a project's ultimate success.   Include:
1. Financial perspective (on time, on budget,etc)
2. Business/customer perspective (met requirements, ease of use, etc)
3. Quality perspective (number/severity of post implementation problems, performance, etc)
4. Project team (employee) perspective. (good use of skills, challenging, good teamwork, etc)</description>
		<content:encoded><![CDATA[<p>I agree with Steven in that these are questions to be answered before a project begins.  A &#8216;balanced scorecard&#8217; that is focused on the project&#8217;s stakeholders determines a project&#8217;s ultimate success.   Include:<br />
1. Financial perspective (on time, on budget,etc)<br />
2. Business/customer perspective (met requirements, ease of use, etc)<br />
3. Quality perspective (number/severity of post implementation problems, performance, etc)<br />
4. Project team (employee) perspective. (good use of skills, challenging, good teamwork, etc)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Levy</title>
		<link>http://www.pmhut.com/10-questions-that-determine-a-projects-success/comment-page-1#comment-16120</link>
		<dc:creator>Steven Levy</dc:creator>
		<pubDate>Thu, 28 Jan 2010 19:27:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/?p=4690#comment-16120</guid>
		<description>This is the stuff that belongs in a Project Charter. I'd add at least two more items. 1) What does "Done" look like? What are the two or three CSFs -- critical success factors -- that will determine whether you're successful overall? 2) Who are the stakeholders? The sponsor is one, of course, but who else?

Then get the stakeholders to sign -- or at least sign off on -- the Charter.

The Project Charter should be a formal document (or set of &lt;em&gt;short&lt;/em&gt; documents) for formal and/or larger projects. For some projects, especially those not under formal project management (some organizations are averse to formal project management, but the PM tasks need to get done anyway in another guise), the PM should still collect the info in the Charter; in such cases the Charter might be structured as a series of EMails.

  -- Steven B. Levy
     Author, &lt;a href='http://www.amazon.com/Legal-Project-Management-Schedules-Maintain/dp/1449928641' rel="nofollow"&gt;&lt;em&gt;Legal Project Management: Control Costs, Meet Schedules, Manage Risks, and Maintain Sanity&lt;/em&gt;&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>This is the stuff that belongs in a Project Charter. I&#8217;d add at least two more items. 1) What does &#8220;Done&#8221; look like? What are the two or three CSFs &#8212; critical success factors &#8212; that will determine whether you&#8217;re successful overall? 2) Who are the stakeholders? The sponsor is one, of course, but who else?</p>
<p>Then get the stakeholders to sign &#8212; or at least sign off on &#8212; the Charter.</p>
<p>The Project Charter should be a formal document (or set of <em>short</em> documents) for formal and/or larger projects. For some projects, especially those not under formal project management (some organizations are averse to formal project management, but the PM tasks need to get done anyway in another guise), the PM should still collect the info in the Charter; in such cases the Charter might be structured as a series of EMails.</p>
<p>  &#8212; Steven B. Levy<br />
     Author, <a href='http://www.amazon.com/Legal-Project-Management-Schedules-Maintain/dp/1449928641' rel="nofollow"><em>Legal Project Management: Control Costs, Meet Schedules, Manage Risks, and Maintain Sanity</em></a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

