<?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 Success Principles</title>
	<atom:link href="http://www.pmhut.com/project-success-principles/feed" rel="self" type="application/rss+xml" />
	<link>http://www.pmhut.com/project-success-principles</link>
	<description></description>
	<pubDate>Mon, 22 Mar 2010 11:35:18 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kristina Podnar</title>
		<link>http://www.pmhut.com/project-success-principles/comment-page-1#comment-1086</link>
		<dc:creator>Kristina Podnar</dc:creator>
		<pubDate>Wed, 04 Feb 2009 11:44:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.pmhut.com/project-success-principles#comment-1086</guid>
		<description>Well said Rino!  I couldn't agree more, and most often see projects, large or small, failing because of what I call strategy (but purpose works!) and measurement (or tracking). It is incredible that the project management field has "matured" to such an extent, and yet there are still projects that do not follow these core steps.

On the demo front, I would say that there are (unfortunately) projects where you may not be able to demo until late in the game. If that is the case, still meet with stakeholders to review development towards functionality (even if it is via diagrams, HTML dummy pages, or stick figures on the paper). Because, as you pointed out, this gives everyone the opportunity to ensure that the project is moving in the right direction and that wrong assumptions are not being made.

Thanks for the post!  Good review of great basics, that are often forgotten.

Kristina</description>
		<content:encoded><![CDATA[<p>Well said Rino!  I couldn&#8217;t agree more, and most often see projects, large or small, failing because of what I call strategy (but purpose works!) and measurement (or tracking). It is incredible that the project management field has &#8220;matured&#8221; to such an extent, and yet there are still projects that do not follow these core steps.</p>
<p>On the demo front, I would say that there are (unfortunately) projects where you may not be able to demo until late in the game. If that is the case, still meet with stakeholders to review development towards functionality (even if it is via diagrams, HTML dummy pages, or stick figures on the paper). Because, as you pointed out, this gives everyone the opportunity to ensure that the project is moving in the right direction and that wrong assumptions are not being made.</p>
<p>Thanks for the post!  Good review of great basics, that are often forgotten.</p>
<p>Kristina</p>
]]></content:encoded>
	</item>
</channel>
</rss>
