<?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: Promises and Prescriptions</title>
	<link>http://www.reformingprojectmanagement.com/2004/02/17/321/</link>
	<description>The magazine for the project age</description>
	<pubDate>Sun, 07 Sep 2008 23:22:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Paulo Napolitano
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/02/17/321/#comment-190</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/02/17/321/#comment-190</guid>
					<description>
        I would like to comment about the first complaint: Rework

I see rework as a work that is required to reshape the interdependence of sub activities that are related to a process or project in a way to keep the flow continuous.
I know that we can have rework as a result of a lack of knowledge or mistakes but most of the time they are  result of the uncertainty of the process that we are managing and we must not see them as a problem.
Projects without reworks are not flowing.
I would be very glad if you could share your point of view!
      </description>
		<content:encoded><![CDATA[<p>I would like to comment about the first complaint: Rework</p>
<p>I see rework as a work that is required to reshape the interdependence of sub activities that are related to a process or project in a way to keep the flow continuous.<br />
I know that we can have rework as a result of a lack of knowledge or mistakes but most of the time they are  result of the uncertainty of the process that we are managing and we must not see them as a problem.<br />
Projects without reworks are not flowing.<br />
I would be very glad if you could share your point of view!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
