<?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; Scope</title>
	<atom:link href="http://www.myprojectlessons.com/tag/scope/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>Clarify Terms and Conditions</title>
		<link>http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/</link>
		<comments>http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/#comments</comments>
		<pubDate>Tue, 25 Nov 2008 10:31:55 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[Contract]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Client]]></category>
		<category><![CDATA[conditions]]></category>
		<category><![CDATA[deliverables]]></category>
		<category><![CDATA[details]]></category>
		<category><![CDATA[Scope]]></category>
		<category><![CDATA[terms]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=105</guid>
		<description><![CDATA[Clarify the terms and conditions with the new project manager. If the client changes during a project (or the client project manager changes), then you as the project manager should make sure to clarify all the contract terms and conditions, deliverables, and scope with the new client or client&#8217;s project manager. Obviously the scope will [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/11/know-the-scope-of-your-project/" rel="bookmark">Know the Scope of Your Project</a><!-- (13.9)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/11/clarify-ownership-of-drawings/" rel="bookmark">Clarify Ownership Of Drawings</a><!-- (13.8)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/06/clarify-terminology/" rel="bookmark">Clarify Terminology</a><!-- (10.9)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>Clarify the <strong>terms and conditions </strong>with the new project manager.</p>
<p>If the client changes during a project (or the client project manager changes), then you as the project manager should make sure to clarify all the contract terms and conditions, deliverables, and scope with the new client or client&#8217;s project manager.</p>
<p>Obviously the scope will need to be clarified, but it is also important to go over with the new client or project manager all the finer details of the contract to avoid any uncertainty or surprises on their part.</p>
<p>It is not ideal just to let them read the contract. Good communication is important and a proper discussion of the existing terms will make a smoother business relationship.</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/11/know-the-scope-of-your-project/" rel="bookmark">Know the Scope of Your Project</a><!-- (13.9)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/11/clarify-ownership-of-drawings/" rel="bookmark">Clarify Ownership Of Drawings</a><!-- (13.8)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/06/clarify-terminology/" rel="bookmark">Clarify Terminology</a><!-- (10.9)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Know the Scope of Your Project</title>
		<link>http://www.myprojectlessons.com/2008/11/know-the-scope-of-your-project/</link>
		<comments>http://www.myprojectlessons.com/2008/11/know-the-scope-of-your-project/#comments</comments>
		<pubDate>Wed, 19 Nov 2008 11:15:40 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Contract]]></category>
		<category><![CDATA[Scope]]></category>
		<category><![CDATA[stakeholders]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=91</guid>
		<description><![CDATA[Know the scope of your contract. Read it often. As a project manager it rules your role on that project. Make sure you clarify the scope with all stakeholders to be sure you all understand it the same way. (Client, designers, drafters, managers, contractors, etc). Related Posts Clarify Terms and Conditions Scope Creep Document Changes [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/" rel="bookmark">Clarify Terms and Conditions</a><!-- (15.1)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/scope-creep/" rel="bookmark">Scope Creep</a><!-- (10.7)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-changes-in-scope/" rel="bookmark">Document Changes in Scope</a><!-- (10.5)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p><strong>Know the scope of your contract</strong>. Read it often. As a project manager it rules your role on that project.</p>
<p>Make sure you clarify the scope with all stakeholders to be sure you all understand it the same way. (Client, designers, drafters, managers, contractors, etc).</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/" rel="bookmark">Clarify Terms and Conditions</a><!-- (15.1)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/scope-creep/" rel="bookmark">Scope Creep</a><!-- (10.7)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-changes-in-scope/" rel="bookmark">Document Changes in Scope</a><!-- (10.5)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2008/11/know-the-scope-of-your-project/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Clear Duties in Contract</title>
		<link>http://www.myprojectlessons.com/2008/11/clear-duties-in-contract/</link>
		<comments>http://www.myprojectlessons.com/2008/11/clear-duties-in-contract/#comments</comments>
		<pubDate>Tue, 18 Nov 2008 10:22:12 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Contract]]></category>
		<category><![CDATA[Scope]]></category>
		<category><![CDATA[duties]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=88</guid>
		<description><![CDATA[Make strong, clear language in the contract documents so that your company&#8217;s duties are very clear. This avoids problems later on in the project. By making the duties clear (the scope) you avoid the problem of extra duties being added to the project that are not paid for. A clear scope should be clear, and [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/10/clear-specifications/" rel="bookmark">Clear Specifications</a><!-- (9.3)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/07/addition-clause-in-contract/" rel="bookmark">Addition Clause in Contract</a><!-- (9.2)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/" rel="bookmark">Clarify Terms and Conditions</a><!-- (8.7)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>Make <strong>strong, clear language</strong> in the contract documents so that your company&#8217;s <strong>duties are very clear</strong>.</p>
<p>This avoids problems later on in the project.<br />
By making the duties clear (the scope) you avoid the problem of extra duties being added to the project that are not paid for.</p>
<p>A clear scope should be clear, and understood by both parties in the contract.</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/10/clear-specifications/" rel="bookmark">Clear Specifications</a><!-- (9.3)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/07/addition-clause-in-contract/" rel="bookmark">Addition Clause in Contract</a><!-- (9.2)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/11/clarify-terms-and-conditions/" rel="bookmark">Clarify Terms and Conditions</a><!-- (8.7)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2008/11/clear-duties-in-contract/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scope Creep</title>
		<link>http://www.myprojectlessons.com/2008/10/scope-creep/</link>
		<comments>http://www.myprojectlessons.com/2008/10/scope-creep/#comments</comments>
		<pubDate>Thu, 30 Oct 2008 10:40:50 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Scope]]></category>
		<category><![CDATA[Cost]]></category>
		<category><![CDATA[Time]]></category>
		<category><![CDATA[variations]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=43</guid>
		<description><![CDATA[Be careful of scope creep. Scope creep is where small additions or changes add up to contribute a larger and larger change in the scope of the project, often affecting delivery time and costs. A few lessons I learnt: If scope is changed or more is asked for, submit variations before proceeding. If scope is [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-changes-in-scope/" rel="bookmark">Document Changes in Scope</a><!-- (14.2)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/document-all-changes-variations-and-agreements/" rel="bookmark">Document all Changes, Variations, and Agreements</a><!-- (10.5)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/01/get-instructions-in-writing/" rel="bookmark">Get Instructions in Writing</a><!-- (10.5)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p><strong>Be careful of scope creep.</strong></p>
<p>Scope creep is where small additions or changes add up to contribute a larger and larger change in the scope of the project, often affecting delivery time and costs.</p>
<p>A few lessons I learnt:</p>
<ul>
<li>If scope is changed or more is asked for, submit variations before proceeding.</li>
</ul>
<ul>
<li>If scope is changed you should ask for more money and more time.</li>
</ul>
<ul>
<li>Always be aware that the time to completion may change with a changed scope.</li>
</ul>
<ul>
<li>Even small additions add up to enough to increase the time to completion.</li>
</ul>
<ul>
<li>Make sure to get written approval from the client before additions, variations, or scope change.</li>
</ul>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-changes-in-scope/" rel="bookmark">Document Changes in Scope</a><!-- (14.2)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/document-all-changes-variations-and-agreements/" rel="bookmark">Document all Changes, Variations, and Agreements</a><!-- (10.5)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/01/get-instructions-in-writing/" rel="bookmark">Get Instructions in Writing</a><!-- (10.5)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2008/10/scope-creep/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

