<?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>My Project Management Lessons &#187; specs</title>
	<atom:link href="http://www.myprojectlessons.com/tag/specs/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.myprojectlessons.com</link>
	<description>Lessons learned in Project Management</description>
	<lastBuildDate>Sat, 28 Nov 2009 02:34:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
		<item>
		<title>Clear Specifications</title>
		<link>http://www.myprojectlessons.com/2008/10/clear-specifications/</link>
		<comments>http://www.myprojectlessons.com/2008/10/clear-specifications/#comments</comments>
		<pubDate>Mon, 27 Oct 2008 10:54:54 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[specification]]></category>
		<category><![CDATA[specs]]></category>
		<category><![CDATA[standard]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=30</guid>
		<description><![CDATA[An important lesson I have learned if you are on the design side of the project. Make the specifications clear. Unclear or contradictory specifications just end up leading to having to continually answer request for clarifications, and can also lead to contractors making extra claims for variations because  of different interpretations of the specs. If [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/08/outdated-specifications/" rel="bookmark">Outdated Specifications</a><!-- (18.7)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/07/clear-roles-and-responsibilities/" rel="bookmark">Clear Roles and Responsibilities.</a><!-- (8.5)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/check-standards-for-pipes/" rel="bookmark">Check Standards for Pipes</a><!-- (8.4)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>An important lesson I have learned if you are on the design side of the project.</p>
<p><strong>Make the specifications clear.</strong></p>
<p>Unclear or contradictory specifications just end up leading to having to continually answer request for clarifications, and can also lead to contractors making extra claims for variations because  of different interpretations of the specs.</p>
<p>If you refer to standards, make sure to check that the standard you refer to is the current/newest one. If you specify an old standard (easy to do if you are using your organisations standard specifications) you could be specifying that the contractor do the project in a way that does not meet new requirements. This may mean they will claim for extra costs to cover changes to meet the newest standards or that the resultant product doesn&#8217;t perform to expected requirements.</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/08/outdated-specifications/" rel="bookmark">Outdated Specifications</a><!-- (18.7)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/07/clear-roles-and-responsibilities/" rel="bookmark">Clear Roles and Responsibilities.</a><!-- (8.5)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/check-standards-for-pipes/" rel="bookmark">Check Standards for Pipes</a><!-- (8.4)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2008/10/clear-specifications/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

