<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.5" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Project e-Tip 035: Take the Time to Plan Outcomes before Activity</title>
	<link>http://www.reformingprojectmanagement.com/2004/09/08/414/</link>
	<description>The magazine for the project age</description>
	<pubDate>Thu, 20 Nov 2008 22:19:44 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Dave Whelbourn
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/09/08/414/#comment-252</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/09/08/414/#comment-252</guid>
					<description>
        To aid this PM's have to stop thinking in terms of a Work Breakdown Structure and move to thinking of a Product Breakdown Structure that defines ALL the products a project will create. This includes management products(Plans, risk registers etc...) as well as quality products(the deliverables).

After defining the PBS you can then build a product flow diagram to identify true dependencies. PM's who want to explore this idea further should review the PRINCE2 Project Management methodology.
      </description>
		<content:encoded><![CDATA[<p>To aid this PM&#8217;s have to stop thinking in terms of a Work Breakdown Structure and move to thinking of a Product Breakdown Structure that defines ALL the products a project will create. This includes management products(Plans, risk registers etc&#8230;) as well as quality products(the deliverables).</p>
<p>After defining the PBS you can then build a product flow diagram to identify true dependencies. PM&#8217;s who want to explore this idea further should review the PRINCE2 Project Management methodology.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
