<?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: Schedule Game column is up</title>
	<atom:link href="http://jrothman.com/blog/mpd/2007/07/schedule-game-column-is-up.html/feed" rel="self" type="application/rss+xml" />
	<link>http://jrothman.com/blog/mpd/2007/07/schedule-game-column-is-up.html</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<pubDate>Thu, 08 Jan 2009 13:52:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kenneth P. Katz</title>
		<link>http://jrothman.com/blog/mpd/2007/07/schedule-game-column-is-up.html/comment-page-1#comment-627</link>
		<dc:creator>Kenneth P. Katz</dc:creator>
		<pubDate>Wed, 25 Jul 2007 00:52:06 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=7966#comment-627</guid>
		<description>The unbreakable rule* on every project that I manage is that there are only three states for every task.
1. Not yet started.
2. In work (started and incomplete).
3. Completed.
None of this 90% complete nonsense. As long as your decompose your work into small enough work packages and define what "completed" means in an unambigous way, this works very well.
* The exception is when the % of work accomplished can be measured in an unambiguous way. Example: you are loading 50 data tapes to online storage. Rather than make this 50 different tasks (rather unwieldy and cluttered), make it one task and count the loading of each tape as 2% progress.</description>
		<content:encoded><![CDATA[<p>The unbreakable rule* on every project that I manage is that there are only three states for every task.<br />
1. Not yet started.<br />
2. In work (started and incomplete).<br />
3. Completed.<br />
None of this 90% complete nonsense. As long as your decompose your work into small enough work packages and define what &#8220;completed&#8221; means in an unambigous way, this works very well.<br />
* The exception is when the % of work accomplished can be measured in an unambiguous way. Example: you are loading 50 data tapes to online storage. Rather than make this 50 different tasks (rather unwieldy and cluttered), make it one task and count the loading of each tape as 2% progress.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
