<?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>mentis vulgaris &#187; Consulting</title>
	<atom:link href="http://numainnovations.com/mentis-vulgaris/category/consulting/feed/" rel="self" type="application/rss+xml" />
	<link>http://numainnovations.com/mentis-vulgaris</link>
	<description>Simple thoughts about software, business and one or two other things</description>
	<lastBuildDate>Fri, 03 Sep 2010 22:51:47 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>One Step Closer to Expertise</title>
		<link>http://numainnovations.com/mentis-vulgaris/jason/software-development/one-step-closer-to-expertise/</link>
		<comments>http://numainnovations.com/mentis-vulgaris/jason/software-development/one-step-closer-to-expertise/#comments</comments>
		<pubDate>Tue, 29 Jul 2008 11:59:14 +0000</pubDate>
		<dc:creator>Jason Smith</dc:creator>
				<category><![CDATA[Consulting]]></category>
		<category><![CDATA[Software Development]]></category>
		<category><![CDATA[brooks law]]></category>
		<category><![CDATA[classic mistake]]></category>

		<guid isPermaLink="false">http://numainnovations.com/mentis-vulgaris/?p=15</guid>
		<description><![CDATA[An expert is a person who has made all the mistakes that can be made in a very narrow field. &#8212; Niels Bohr
Early in my consulting career, I experienced losing a client in mid project.  While I&#8217;d love to blame the client and some hideous set of working conditions, it was most definitely my mistake.
The [...]]]></description>
			<content:encoded><![CDATA[<blockquote><p><em>An expert is a person who has made all the mistakes that can be made in a very narrow field.</em> &#8212; Niels Bohr</p></blockquote>
<p>Early in my consulting career, I experienced losing a client in mid project.  While I&#8217;d love to blame the client and some hideous set of working conditions, it was most definitely my mistake.</p>
<p><span id="more-15"></span>The mistake: when I was brought on to replace the old technical lead, I didn&#8217;t insist on resetting the delivery schedule.  I mumbled something about it being &#8220;aggressive&#8221;, but ultimately accepted it as it was.</p>
<p>I also knew <a href="http://en.wikipedia.org/wiki/Brooks%27s_law">Brooks&#8217; Law</a> most likely made the schedule a fiction.</p>
<blockquote><p><em>Adding manpower to a late software project makes it later.</em><br />
&#8211; <a href="http://www.amazon.com/gp/redirect.html?ie=UTF8&amp;location=http%3A%2F%2Fwww.amazon.com%2FMythical-Man-Month-Software-Engineering-Anniversary%2Fdp%2F0201835959%3Fie%3DUTF8%26s%3Dbooks%26qid%3D1216911023%26sr%3D8-1&amp;tag=nuinll-20&amp;linkCode=ur2&amp;camp=1789&amp;creative=9325">Frederick P. Brooks, Jr. <em>The Mythical Man Month</em>. 1995. Addison-Wesley</a><img style="border:none !important; margin:0px !important;" src="http://www.assoc-amazon.com/e/ir?t=nuinll-20&amp;l=ur2&amp;o=1" border="0" alt="" width="1" height="1" /></p></blockquote>
<p>For some reason, the law is usually invoked on larger projects, but it affects projects of all sizes, including this particular two person one.   In a nutshell, it stems from the fact that the new person on a team takes time to come up to speed.  He must learn the requirements, design, code and process (especially if he is to <em>lead </em>the team).  Others on the team must also take time out of their schedule to educate the new guy.  So the schedule slips some more.</p>
<p>But my mistake wasn&#8217;t ignoring Brooks&#8217; Law.  It was more insidious.  I failed to live up to my responsibility to the client to inform him as soon as I knew of the problem &#8212; way back when he considered hiring me.</p>
<p>This was one of the first clients I landed. It was a <em>big </em>one.  I did not want to be the messenger bearing bad news. Not right out of the gates.  Surely, if I tell them something they don&#8217;t want to hear before I&#8217;ve established any credibility, they might &#8230; umm &#8230; not hire me.</p>
<p>So I kept my mouth shut, got hired, went to work and hoped for the best.</p>
<blockquote><p><em>Hope is not a strategy &#8212; Hillary Clinton</em></p></blockquote>
<p>As we cleared each milestone, I reset the schedule for the next set of features.  Unfortunately, what the client saw was the schedule slipping a bit more each time.</p>
<p>So they hired a new guy and let me go.</p>
<p>Moral &#8212; always, always, <em>always</em> raise concerns early.  Even if it means I won&#8217;t get the job (which certainly beats disappointing the client and losing them later).</p>
<p>Meanwhile, I&#8217;m a mistake or two closer to being an expert.</p>
]]></content:encoded>
			<wfw:commentRss>http://numainnovations.com/mentis-vulgaris/jason/software-development/one-step-closer-to-expertise/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

