<?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: Managing the &#8220;weekly&#8221; (highlight) report</title>
	<atom:link href="http://www.magnone.eu/archives/2640/feed" rel="self" type="application/rss+xml" />
	<link>http://www.magnone.eu/archives/2640</link>
	<description>Information is for projects like water for life. The success lies in a careful management of needs.</description>
	<lastBuildDate>Wed, 18 Nov 2009 08:15:10 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Glen B. Alleman</title>
		<link>http://www.magnone.eu/archives/2640/comment-page-1#comment-63</link>
		<dc:creator>Glen B. Alleman</dc:creator>
		<pubDate>Thu, 22 Oct 2009 02:52:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.magnone.eu/?p=2640#comment-63</guid>
		<description>We&#039;ve learned through hard won experience that traditional status reports follow the example here.
&quot;Deliverables Based Planning(sm)&quot; is our approach to planning and management of proejcts. The Plan of the Week and the Plan of the Month are the basis of the measure of Physical Percent Complete.

When you define the physical tangible outcomes for the &quot;close of business&quot; (COB) for the week, the status report becomes a report on &quot;what did you do this week, that you said you were going to do?&quot;

For uncompleted - but promised - deliverables on a weekly basis, these are moved to a future period. This action mortgages the future with partially completed commitments. 

This is the purpose of the deliverables view of the project rather than one that is &quot;effort.&quot; 

In the end the guiding phrase is &quot;never confuse effort with results.&quot; The traditional status report describes the &quot;effort&quot; performed during the week. With a deliverables only plan and related status, the effort is a secondary status (cost) and the 100% completion of the planned deliverables speaks for the progress by itself.</description>
		<content:encoded><![CDATA[<p>We&#8217;ve learned through hard won experience that traditional status reports follow the example here.<br />
&#8220;Deliverables Based Planning(sm)&#8221; is our approach to planning and management of proejcts. The Plan of the Week and the Plan of the Month are the basis of the measure of Physical Percent Complete.</p>
<p>When you define the physical tangible outcomes for the &#8220;close of business&#8221; (COB) for the week, the status report becomes a report on &#8220;what did you do this week, that you said you were going to do?&#8221;</p>
<p>For uncompleted &#8211; but promised &#8211; deliverables on a weekly basis, these are moved to a future period. This action mortgages the future with partially completed commitments. </p>
<p>This is the purpose of the deliverables view of the project rather than one that is &#8220;effort.&#8221; </p>
<p>In the end the guiding phrase is &#8220;never confuse effort with results.&#8221; The traditional status report describes the &#8220;effort&#8221; performed during the week. With a deliverables only plan and related status, the effort is a secondary status (cost) and the 100% completion of the planned deliverables speaks for the progress by itself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

