<?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; changes</title>
	<atom:link href="http://www.myprojectlessons.com/tag/changes/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>Good Document System</title>
		<link>http://www.myprojectlessons.com/2009/04/good-document-system/</link>
		<comments>http://www.myprojectlessons.com/2009/04/good-document-system/#comments</comments>
		<pubDate>Sat, 11 Apr 2009 03:16:46 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Cost]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Planning]]></category>
		<category><![CDATA[accounting]]></category>
		<category><![CDATA[budget]]></category>
		<category><![CDATA[changes]]></category>
		<category><![CDATA[expenses]]></category>
		<category><![CDATA[forecast]]></category>
		<category><![CDATA[labour]]></category>
		<category><![CDATA[statistics]]></category>
		<category><![CDATA[system]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=331</guid>
		<description><![CDATA[If you have control of the system at the start of a project, make sure the project (or even at the program level, project office level, or company level) uses a document and accounting system that can record and output everything. This would include costs, labour, forecasts, statistics, billing, budget, expenses, changes etc. It should [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-design-changes-and-delays/" rel="bookmark">Document Design Changes and Delays</a><!-- (16.1)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/08/eliminate-unnecessary-features/" rel="bookmark">Eliminate Unnecessary Features</a><!-- (12)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/04/record-your-achievements/" rel="bookmark">Record Your Achievements</a><!-- (11)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>If you have control of the system at the start of a project, make sure the project (or even at the program level, project office level, or company level) uses a document and accounting system that can record and output everything.</p>
<p>This would include costs, labour, forecasts, statistics, billing, budget, expenses, changes etc.</p>
<p>It should be able to output things like:</p>
<ul>
<li>Weekly reports.</li>
<li> Monthly cost summary</li>
<li> Invoices</li>
<li> Labour costs for a period</li>
<li> Expense breakdowns</li>
<li> Cost to date</li>
<li> Variance</li>
<li> Total cost at completion</li>
</ul>
<p>This should all be available from one package or a number of modules that are automatically linked together. You do not want to have multiple spreadsheets that people record things in that are not linked. The  result should be a significant reduction in paperwork.</p>
<p>Certain inputs could only be allowed by certain people (by log in), such as:</p>
<ul>
<li>Accounts (accountant)</li>
<li> Billing</li>
<li> Labour (site manager)</li>
<li> Design hours (design manager)</li>
</ul>
<p>Individual hours by each person could be input (linked) from time sheets. All staff/employees should have adequate training so that the system is used properly</p>
<p>To start with, I recommend looking at the <a title="List of Project Managem Software" href="http://en.wikipedia.org/wiki/List_of_project_management_software">list of project management software</a> at Wikipedia.</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-design-changes-and-delays/" rel="bookmark">Document Design Changes and Delays</a><!-- (16.1)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/08/eliminate-unnecessary-features/" rel="bookmark">Eliminate Unnecessary Features</a><!-- (12)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/04/record-your-achievements/" rel="bookmark">Record Your Achievements</a><!-- (11)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2009/04/good-document-system/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Document Changes in Scope</title>
		<link>http://www.myprojectlessons.com/2009/03/document-changes-in-scope/</link>
		<comments>http://www.myprojectlessons.com/2009/03/document-changes-in-scope/#comments</comments>
		<pubDate>Mon, 02 Mar 2009 09:31:04 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Client]]></category>
		<category><![CDATA[Documentation]]></category>
		<category><![CDATA[Scope]]></category>
		<category><![CDATA[changes]]></category>

		<guid isPermaLink="false">http://www.myprojectlessons.com/?p=193</guid>
		<description><![CDATA[If, during a project, the client realises a mistake in the scope or specs or one is pointed out to the client and the client authorizes or instructs a change in scope, the changes should be fully documented. These changes should be marked on all copies of the scope or spec documents, and also on [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/10/scope-creep/" rel="bookmark">Scope Creep</a><!-- (12.6)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-design-changes-and-delays/" rel="bookmark">Document Design Changes and Delays</a><!-- (12.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.4)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p>If, during a project, the client realises a mistake in the scope or specs or one is pointed out to the client and the client authorizes or instructs a change in scope, the <strong>changes should be fully documented</strong>. These changes should be marked on all copies of the scope or spec documents, and also on digital versions of the scope or specs.</p>
<p>If a change is not marked on every copy, someone from the project team might work with an old copy of the scope or spec and thus not follow the new scope.</p>
<p>It is important that if people have printed versions at their desks, then those versions are also altered or reprinted.</p>
<p>This applies to corrections, not new scope. New, additional scope should be stored in a location (electronically and in hard copy if necessary) that is known and accessible to all the project team.</p>
<p>It is important that any extra scope be regularly checked and that the project team is aware of what is and is not included in the scope (both original and new).</p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2008/10/scope-creep/" rel="bookmark">Scope Creep</a><!-- (12.6)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-design-changes-and-delays/" rel="bookmark">Document Design Changes and Delays</a><!-- (12.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.4)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2009/03/document-changes-in-scope/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Document all Changes, Variations, and Agreements</title>
		<link>http://www.myprojectlessons.com/2008/10/document-all-changes-variations-and-agreements/</link>
		<comments>http://www.myprojectlessons.com/2008/10/document-all-changes-variations-and-agreements/#comments</comments>
		<pubDate>Tue, 14 Oct 2008 08:37:14 +0000</pubDate>
		<dc:creator>michael</dc:creator>
				<category><![CDATA[Documentation]]></category>
		<category><![CDATA[changes]]></category>

		<guid isPermaLink="false">http://myprojectlessons.com/?p=18</guid>
		<description><![CDATA[Document all changes, variations, agreements etc. If it is done verbally, put it in writing and send to the person involved. Make sure the client / stakeholder is sent this documentation. This will protect yourself and your company in the event of disagreement or a claim. It will clarify intentions. Important for QA documentation, and [...]

<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/02/copy-minutes-of-meetings-to-attendees/" rel="bookmark">Copy Minutes of Meetings to Attendees</a><!-- (18.5)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-changes-in-scope/" rel="bookmark">Document Changes in Scope</a><!-- (11.9)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/document-all-communication/" rel="bookmark">Document All Client Communication</a><!-- (11.5)--></li>
	</ol>
]]></description>
			<content:encoded><![CDATA[<p><strong>Document all changes, variations, agreements</strong> etc. If it is done verbally, put it in writing and send to the person involved. Make sure the client / stakeholder is sent this documentation.</p>
<ul>
<li>This will protect yourself and your company in the event of disagreement or a claim.</li>
<li>It will clarify intentions.</li>
<li>Important for QA documentation, and for scope adherence, and legal.</li>
<li>Get approval in writing for changes or variations.</li>
<li>Document on the assumption that “if it’s not in writing, it didn’t happen”.</li>
<li>At least prepare a written confirmation of verbal instructions and copy to the client.</li>
<li>Document your efforts to meet client goals.</li>
<li>Get and distribute copies of minutes of meetings with the client.</li>
</ul>
<p><!--[endif]--></p>


<h3>Related Posts</h3>
<ol>
		<li><a href="http://www.myprojectlessons.com/2009/02/copy-minutes-of-meetings-to-attendees/" rel="bookmark">Copy Minutes of Meetings to Attendees</a><!-- (18.5)--></li>
		<li><a href="http://www.myprojectlessons.com/2009/03/document-changes-in-scope/" rel="bookmark">Document Changes in Scope</a><!-- (11.9)--></li>
		<li><a href="http://www.myprojectlessons.com/2008/10/document-all-communication/" rel="bookmark">Document All Client Communication</a><!-- (11.5)--></li>
	</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.myprojectlessons.com/2008/10/document-all-changes-variations-and-agreements/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

