<?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: Looking for a Reference</title>
	<atom:link href="http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.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>
	<lastBuildDate>Fri, 18 May 2012 15:02:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: James A. Ward</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-28</link>
		<dc:creator>James A. Ward</dc:creator>
		<pubDate>Mon, 27 Dec 2004 06:03:33 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-28</guid>
		<description>In &quot;Productivity Management In The Development Of Computer Applications&quot; by John E. Keane, Marilyn Keane and Mark Teagan the following appears: &quot;Actual Productive Time: Expecting a full eight hours of productivity per day is unreasonable because of interruptions, time devoted to nonproject communication, personal business, and other unscheduled activities. A Bell Labs study indicated that approximately 30 % of a programmer&#039;s day is spent in such nonproject activities. In addition, training, holidays, vacations, illness, and other absences have a direct effect on elapsed time and should be provided for in estimates. Keane uses a figure of 80%; IBM 75%.&quot;
As this was written in 1984, we did not have e-mail and surfing the net to deal with. I have been teaching the concept of &quot;productive time&quot; for years. I hope the above helps.</description>
		<content:encoded><![CDATA[<p>In &#8220;Productivity Management In The Development Of Computer Applications&#8221; by John E. Keane, Marilyn Keane and Mark Teagan the following appears: &#8220;Actual Productive Time: Expecting a full eight hours of productivity per day is unreasonable because of interruptions, time devoted to nonproject communication, personal business, and other unscheduled activities. A Bell Labs study indicated that approximately 30 % of a programmer&#8217;s day is spent in such nonproject activities. In addition, training, holidays, vacations, illness, and other absences have a direct effect on elapsed time and should be provided for in estimates. Keane uses a figure of 80%; IBM 75%.&#8221;<br />
As this was written in 1984, we did not have e-mail and surfing the net to deal with. I have been teaching the concept of &#8220;productive time&#8221; for years. I hope the above helps.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keith ray</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-29</link>
		<dc:creator>keith ray</dc:creator>
		<pubDate>Sat, 18 Dec 2004 17:31:54 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-29</guid>
		<description>It&#039;s probably not in any books that I&#039;ve read, but on mailing lists and maybe other web-resources, XP gurus have said that pair programming is tiring enough that most XP teams only do pair-programming 6 hours a day.</description>
		<content:encoded><![CDATA[<p>It&#8217;s probably not in any books that I&#8217;ve read, but on mailing lists and maybe other web-resources, XP gurus have said that pair programming is tiring enough that most XP teams only do pair-programming 6 hours a day.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne Allen</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-31</link>
		<dc:creator>Wayne Allen</dc:creator>
		<pubDate>Fri, 17 Dec 2004 21:14:45 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-31</guid>
		<description>This may not be exactly what you were looking for, but is in the same spirit with some numbers behind it.
http://www.caseplace.org/cases3117/cases_show.htm?doc_id=96442</description>
		<content:encoded><![CDATA[<p>This may not be exactly what you were looking for, but is in the same spirit with some numbers behind it.<br />
<a href="http://www.caseplace.org/cases3117/cases_show.htm?doc_id=96442" rel="nofollow">http://www.caseplace.org/cases3117/cases_show.htm?doc_id=96442</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jared</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-27</link>
		<dc:creator>Jared</dc:creator>
		<pubDate>Fri, 17 Dec 2004 07:10:18 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-27</guid>
		<description>I&#039;m sure I&#039;ve read it too, but can&#039;t remember where.  Any references in Peopleware?
Here&#039;s a non-technical reference:
http://www.context.org/ICLIB/IC37/Hunnicut.htm
&quot;Through the depression years, the six-hour day functioned as W.K. Kellogg and Lewis J. Brown, the company president, hoped. Jobs were created as the company payroll grew. Plant employees seemed delighted to have more time of their own, especially so since their weekly paychecks were only a little smaller. Workers were paid for seven hours during the first year of the six-hour day, but beginning in the second year, total wages were raised back to the nominal level of the eight-hour day.
Productivity was up, both because of the introduction of new technology and because of Kellogg&#039;s innovative approach to hours and work incentives. In essence, the management of Kellogg&#039;s was sharing the benefits of that increased productivity with the workers in the form of free time.&quot;</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure I&#8217;ve read it too, but can&#8217;t remember where.  Any references in Peopleware?<br />
Here&#8217;s a non-technical reference:<br />
<a href="http://www.context.org/ICLIB/IC37/Hunnicut.htm" rel="nofollow">http://www.context.org/ICLIB/IC37/Hunnicut.htm</a><br />
&#8220;Through the depression years, the six-hour day functioned as W.K. Kellogg and Lewis J. Brown, the company president, hoped. Jobs were created as the company payroll grew. Plant employees seemed delighted to have more time of their own, especially so since their weekly paychecks were only a little smaller. Workers were paid for seven hours during the first year of the six-hour day, but beginning in the second year, total wages were raised back to the nominal level of the eight-hour day.<br />
Productivity was up, both because of the introduction of new technology and because of Kellogg&#8217;s innovative approach to hours and work incentives. In essence, the management of Kellogg&#8217;s was sharing the benefits of that increased productivity with the workers in the form of free time.&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Yip</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-32</link>
		<dc:creator>Jason Yip</dc:creator>
		<pubDate>Fri, 17 Dec 2004 02:07:00 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-32</guid>
		<description>This sounds like something Watts Humphries would have written or if not, something he would have measured.</description>
		<content:encoded><![CDATA[<p>This sounds like something Watts Humphries would have written or if not, something he would have measured.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erick Herring</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-30</link>
		<dc:creator>Erick Herring</dc:creator>
		<pubDate>Fri, 17 Dec 2004 00:19:06 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-30</guid>
		<description>Okay, I spent about twenty minutes longer on this than I intended, and I still didn&#039;t find even a close reference to what you seem to want.  I started out thinking that you were paraphrasing, anyway, so I was hoping to find the &quot;real&quot; quote for you.
Having said that, I think you are looking for something by DeMarco and/or Lister (Peopleware 2/e or Slack), Constantine (Constantine on Peoplware, The Peoplware Papers), or Csikszentmahalyi (Flow).  Maybe McConnell, but I doubt it.
I hope this helps jog someone&#039;s memory for you.</description>
		<content:encoded><![CDATA[<p>Okay, I spent about twenty minutes longer on this than I intended, and I still didn&#8217;t find even a close reference to what you seem to want.  I started out thinking that you were paraphrasing, anyway, so I was hoping to find the &#8220;real&#8221; quote for you.<br />
Having said that, I think you are looking for something by DeMarco and/or Lister (Peopleware 2/e or Slack), Constantine (Constantine on Peoplware, The Peoplware Papers), or Csikszentmahalyi (Flow).  Maybe McConnell, but I doubt it.<br />
I hope this helps jog someone&#8217;s memory for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-26</link>
		<dc:creator>Andy</dc:creator>
		<pubDate>Thu, 16 Dec 2004 21:28:23 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-26</guid>
		<description>I was speaking to a co-worker about this several months ago, He was reading:
&quot;Agile software development with scrum&quot; and &quot;Agile project management with scrum&quot; both by Ken Schwaber
Hope this helps you find what you&#039;re looking for.</description>
		<content:encoded><![CDATA[<p>I was speaking to a co-worker about this several months ago, He was reading:<br />
&#8220;Agile software development with scrum&#8221; and &#8220;Agile project management with scrum&#8221; both by Ken Schwaber<br />
Hope this helps you find what you&#8217;re looking for.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Willeke</title>
		<link>http://www.jrothman.com/blog/mpd/2004/12/looking-for-a-reference.html/comment-page-1#comment-25</link>
		<dc:creator>Eric Willeke</dc:creator>
		<pubDate>Thu, 16 Dec 2004 21:26:22 +0000</pubDate>
		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8197#comment-25</guid>
		<description>I think I may have seen this in Robert Glass&#039; 55 Facts &amp; Fallicies book.  Unfortunately, my company is moving this week, so it&#039;s buried at the bottom of a box and I can&#039;t check.</description>
		<content:encoded><![CDATA[<p>I think I may have seen this in Robert Glass&#8217; 55 Facts &#038; Fallicies book.  Unfortunately, my company is moving this week, so it&#8217;s buried at the bottom of a box and I can&#8217;t check.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

