<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Pi/Pi &#187; The Mythical Man Month</title>
	<atom:link href="http://www.pioverpi.net/category/the-mythical-man-month/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pioverpi.net</link>
	<description>...but that&#039;s just one!</description>
	<lastBuildDate>Thu, 24 Nov 2011 05:04:24 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
		<item>
		<title>[TMMM] Ch 15 &#8211; The Other Face</title>
		<link>http://www.pioverpi.net/2010/05/18/tmmm-ch-15-the-other-face/</link>
		<comments>http://www.pioverpi.net/2010/05/18/tmmm-ch-15-the-other-face/#comments</comments>
		<pubDate>Tue, 18 May 2010 06:42:50 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[documentation]]></category>
		<category><![CDATA[the other face]]></category>
		<category><![CDATA[TMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1853</guid>
		<description><![CDATA[&#60;&#60; Ch. 14 &#8211; Hatching a Catastrophe It is not enough to just talk about documentation, the &#8220;masters&#8221; need to show the kids how to do it! What Documentation is Required? To use a program: Purpose: what is the main function, the reason of the program? Environment: machines, hardware configuration, OS configuration, etc. Domain &#38; [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/18/tmmm-ch-15-the-other-face/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 14 &#8211; Hatching a Catastrophe</title>
		<link>http://www.pioverpi.net/2010/05/17/tmmm-ch-14-hatching-a-catastrophe/</link>
		<comments>http://www.pioverpi.net/2010/05/17/tmmm-ch-14-hatching-a-catastrophe/#comments</comments>
		<pubDate>Mon, 17 May 2010 18:22:22 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[hatching a catastrophe]]></category>
		<category><![CDATA[PERT chart]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1850</guid>
		<description><![CDATA[&#60;&#60; Chapter 13: The Whole and the Parts Milestones or Millstones The first step to keeping a schedule is to actually have a schedule. When designing a schedule, you&#8217;ll obviously need milestones.  The milestones must be concrete, specific, measurable events.  Don&#8217;t choose vague tasks like &#8220;coding&#8221; or &#8220;designing&#8221;, because coding is always 90% finished, and [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/17/tmmm-ch-14-hatching-a-catastrophe/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 13 &#8211; The Whole and the Parts</title>
		<link>http://www.pioverpi.net/2010/05/16/tmmm-the-whole-and-the-parts/</link>
		<comments>http://www.pioverpi.net/2010/05/16/tmmm-the-whole-and-the-parts/#comments</comments>
		<pubDate>Sun, 16 May 2010 06:56:49 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[the whole and the parts]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1813</guid>
		<description><![CDATA[&#60;&#60; Chapter 12 Sharp Tools Designing the Bug Out Bug-Proofing the Definition Bugs arise from mismatched assumptions made by the authors of various components.  It is essential, therefore, to maintain conceptual integrity. Careful function definition, careful specification, and disciplined exorcism of frills of function &#38; flights of technique all reduce the number of system bugs [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/16/tmmm-the-whole-and-the-parts/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 12 &#8211; Sharp Tools</title>
		<link>http://www.pioverpi.net/2010/05/15/tmmm-sharp-tools/</link>
		<comments>http://www.pioverpi.net/2010/05/15/tmmm-sharp-tools/#comments</comments>
		<pubDate>Sat, 15 May 2010 06:07:42 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[sharp tools]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1809</guid>
		<description><![CDATA[&#60;&#60; Chapter 11: Plan to Throw One Away Programmers shouldn&#8217;t keep their tools a secret.  The first major problem to a software projects is communication, and personalized tools hamper communication.  Also, the tool lifetime is short due to changes in technology and changes in the language. It is better to have a common development and [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/15/tmmm-sharp-tools/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 11 &#8211; Plan To Throw One Away</title>
		<link>http://www.pioverpi.net/2010/05/14/tmmm-plan-to-throw-one-away/</link>
		<comments>http://www.pioverpi.net/2010/05/14/tmmm-plan-to-throw-one-away/#comments</comments>
		<pubDate>Fri, 14 May 2010 06:11:05 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[planning]]></category>
		<category><![CDATA[throw one away]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1805</guid>
		<description><![CDATA[&#60;&#60; Chapter 10: The Documentary Hypothesis Pilot Plants and Scaling Up Chemists know that a process that works in the lab cannot be implemented in a factory in only one step.  Pilot plants are used to work at an in-between scale. For software projects, the 1st iteration will almost always suck, its big, slow and [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/14/tmmm-plan-to-throw-one-away/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 10 &#8211; Documentary Hypothesis</title>
		<link>http://www.pioverpi.net/2010/05/13/tmmm-documentary-hypothesis/</link>
		<comments>http://www.pioverpi.net/2010/05/13/tmmm-documentary-hypothesis/#comments</comments>
		<pubDate>Thu, 13 May 2010 06:46:57 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[Conway's Law]]></category>
		<category><![CDATA[Documentary Hypothesis]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1802</guid>
		<description><![CDATA[&#60;&#60; Chapter 9: Ten Pounds in a Five Pound Sack The hypothesis: Amid a wash of paper, a small number of documents become critical pivots around which every project&#8217;s management revolves.  These are the manager&#8217;s chief personal tools Documents for a Computer Product (Hardware) Objectives defines the need to be met and the goals, the [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/13/tmmm-documentary-hypothesis/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 9 &#8211; Ten Pounds in a Five-Pound Sack</title>
		<link>http://www.pioverpi.net/2010/05/12/tmmm-ten-pounds-in-a-five-pound-sack/</link>
		<comments>http://www.pioverpi.net/2010/05/12/tmmm-ten-pounds-in-a-five-pound-sack/#comments</comments>
		<pubDate>Wed, 12 May 2010 06:46:55 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[five pound sack]]></category>
		<category><![CDATA[ten pounds]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1797</guid>
		<description><![CDATA[&#60;&#60; Chapter 8: Calling the Shot Programming Space as Cost The system designer puts part of his total hardware resource into resident-program memory when he thinks that it will do more for the user in that form than as adders, disks, etc. No one can criticize a programming system for size per se and at [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/12/tmmm-ten-pounds-in-a-five-pound-sack/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 8 &#8211; Calling the Shot</title>
		<link>http://www.pioverpi.net/2010/05/11/tmmm-calling-the-shot/</link>
		<comments>http://www.pioverpi.net/2010/05/11/tmmm-calling-the-shot/#comments</comments>
		<pubDate>Tue, 11 May 2010 06:02:54 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[calling the shot]]></category>
		<category><![CDATA[TMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1794</guid>
		<description><![CDATA[Chapter 7: Why Did the Towers of Babel Fall? How does one estimate?  Recall that back in Chapter 2 we developed the following ratio: 1/3 planning 1/6 coding 1/4 component test &#38; early systems test 1/4 system test, all components in hand It would be a mistake to estimate the coding first and then develop [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/11/tmmm-calling-the-shot/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 7 &#8211; Why Did The Tower of Babel Fail?</title>
		<link>http://www.pioverpi.net/2010/05/10/tmmm-why-did-the-tower-of-babel-fail/</link>
		<comments>http://www.pioverpi.net/2010/05/10/tmmm-why-did-the-tower-of-babel-fail/#comments</comments>
		<pubDate>Mon, 10 May 2010 06:50:29 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[TMMM]]></category>
		<category><![CDATA[tower of babel]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1779</guid>
		<description><![CDATA[&#60;&#60; Chapter 6: Passing the Word For those unfamiliar with the story of the Tower of Babel, read about it here: http://en.wikipedia.org/wiki/Tower_of_Babel A Management Audit of the Tower of Babel First of all, did the project have the following: A clear mission? Yes, even though it was impossible to do Manpower? Yup Materials? Clay and [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/10/tmmm-why-did-the-tower-of-babel-fail/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>[TMMM] Ch 6 &#8211; Passing the Word</title>
		<link>http://www.pioverpi.net/2010/05/09/tmm-passing-the-word/</link>
		<comments>http://www.pioverpi.net/2010/05/09/tmm-passing-the-word/#comments</comments>
		<pubDate>Sun, 09 May 2010 06:41:49 +0000</pubDate>
		<dc:creator>jama22</dc:creator>
				<category><![CDATA[The Mythical Man Month]]></category>
		<category><![CDATA[passing the word]]></category>
		<category><![CDATA[TMMM]]></category>

		<guid isPermaLink="false">http://www.pioverpi.net/?p=1764</guid>
		<description><![CDATA[&#60;&#60; Chapter 5 &#8211; The Second-System Effect Written Specifications &#8211; The Manual The manual is the external specification of the product, and it is the chief product of the architect The manual must not only describe everything the user does see, including interfaces; it must also refrain from describing what the user does not see.  [...]]]></description>
		<wfw:commentRss>http://www.pioverpi.net/2010/05/09/tmm-passing-the-word/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
	</channel>
</rss>

