<?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: The Added Work of Rework</title>
	<link>http://www.reformingprojectmanagement.com/2004/03/15/341/</link>
	<description>The magazine for the project age</description>
	<pubDate>Wed, 07 Jan 2009 12:16:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.5</generator>

	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/03/15/341/#comment-192</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/03/15/341/#comment-192</guid>
					<description>
        I think he's got it.  :+:  

Adding tasks to 'to do' lists is not the same as promising to complete something by a time certain.  Placing high priority on a to do list task doesn't address evaluating wherewithal, estimating time for completion, and allocating a block of capacity to perform the task.

Thankfully, my wife hasn't caught onto the finer points in this discussion.  Otherwise, there'd be no blogging, the apron would be on, and I'd be mumbling something that I dare not put to print.
      </description>
		<content:encoded><![CDATA[<p>I think he&#8217;s got it.  :+:  </p>
<p>Adding tasks to &#8216;to do&#8217; lists is not the same as promising to complete something by a time certain.  Placing high priority on a to do list task doesn&#8217;t address evaluating wherewithal, estimating time for completion, and allocating a block of capacity to perform the task.</p>
<p>Thankfully, my wife hasn&#8217;t caught onto the finer points in this discussion.  Otherwise, there&#8217;d be no blogging, the apron would be on, and I&#8217;d be mumbling something that I dare not put to print.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Hal
        </title>
		<link>http://www.reformingprojectmanagement.com/2004/03/15/341/#comment-193</link>
		<pubDate>Wed, 31 Dec 1969 16:00:00 +0000</pubDate>
		<guid>http://www.reformingprojectmanagement.com/2004/03/15/341/#comment-193</guid>
					<description>
        Hi Gary,

Thanks for engaging your colleague and offering your views to other readers.  I didn't mean what either of you are saying.   :lol: 

The usual 'to do list' is just that, a list.  There is no way to allocate capacity to the task on the to do list.  Some people assign priority to tasks, but still we see high priority tasks not get done when promised or needed.

Instead of a to do list, how about we start using an 'as promised list' that is part and parcel of ones calendar.  This provides the opportunity to block the time in the calendar.  That one step is the single most important action you can take to increase your reliability.  And even better...you can have your team members do the same.

Oh, and don't be shy about examining team members' allocation of capacity.  You get to see it anyway when you approve their timesheets.  Why not make sure they are doing what they need to do to be reliable?

And for those of you who think I'm being an untrusting micro manager, you are missing the point.  Only half of the tasks promised each week get done as promised.  This creates enormous waste on our projects.  having your team members estimating and allocating time at the moment they promise will have reliability soaring in no time.  Then you can get to work on more value-adding tasks.
      </description>
		<content:encoded><![CDATA[<p>Hi Gary,</p>
<p>Thanks for engaging your colleague and offering your views to other readers.  I didn&#8217;t mean what either of you are saying.    <img src='http://www.reformingprojectmanagement.com/wp-includes/images/smilies/icon_lol.gif' alt=':lol:' class='wp-smiley' />  </p>
<p>The usual &#8216;to do list&#8217; is just that, a list.  There is no way to allocate capacity to the task on the to do list.  Some people assign priority to tasks, but still we see high priority tasks not get done when promised or needed.</p>
<p>Instead of a to do list, how about we start using an &#8216;as promised list&#8217; that is part and parcel of ones calendar.  This provides the opportunity to block the time in the calendar.  That one step is the single most important action you can take to increase your reliability.  And even better&#8230;you can have your team members do the same.</p>
<p>Oh, and don&#8217;t be shy about examining team members&#8217; allocation of capacity.  You get to see it anyway when you approve their timesheets.  Why not make sure they are doing what they need to do to be reliable?</p>
<p>And for those of you who think I&#8217;m being an untrusting micro manager, you are missing the point.  Only half of the tasks promised each week get done as promised.  This creates enormous waste on our projects.  having your team members estimating and allocating time at the moment they promise will have reliability soaring in no time.  Then you can get to work on more value-adding tasks.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
