<?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>epsconsulting.co.uk</title>
	<atom:link href="http://www.epsconsulting.co.uk/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.epsconsulting.co.uk</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Wed, 02 Dec 2009 09:45:58 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Top tips for project control</title>
		<link>http://www.epsconsulting.co.uk/top-tips-for-project-control/</link>
		<comments>http://www.epsconsulting.co.uk/top-tips-for-project-control/#comments</comments>
		<pubDate>Wed, 15 Jul 2009 13:17:28 +0000</pubDate>
		<dc:creator>Rob</dc:creator>
				<category><![CDATA[News]]></category>

		<guid isPermaLink="false">http://www.mktgsuite.com/?p=89</guid>
		<description><![CDATA[The ten Commandments for Project Controls

Use project control systems that are proven &#8211; and already integrated
Set the control methodology from day one &#8211; and stick to it
Understand that the systems will determine the project’s day to day working
Avoid changing project control systems part way through a project’s lifecycle
Do not pick a project control system to [...]]]></description>
			<content:encoded><![CDATA[<div style="width: 425px; text-align: left;"><strong>The ten Commandments for Project Controls</strong></p>
<ol>
<li>Use project control systems that are proven &#8211; and already integrated</li>
<li>Set the control methodology from day one &#8211; and stick to it</li>
<li>Understand that the systems will determine the project’s day to day working</li>
<li>Avoid changing project control systems part way through a project’s lifecycle</li>
<li>Do not pick a project control system to do an enterprise role – or vice versa</li>
<li>Ensure the project control systems are up to the job from day one – if they aren’t, they never will be</li>
<li>Ensure the project control methodology and tools are scaled for the project – don’t use a sledge hammer to crack a nut</li>
<li>Be clear on the project’s required reporting outputs – and that the project control systems  are capable of meeting these  from day one</li>
<li>Understand what levels of breakdown structure a project needs to report at – and that the project control systems are capable of meeting these from day one</li>
<li>Be clear on all user roles and responsibilities involved in operating the project control system – and ensure appropriate training and at elbow support is provided for as long as required</li>
<li>Clearly articulate the principles and benefits behind the project control system – and ensure all project personnel understand these</li>
<li>Implementing a project control system across a project is not a fire and forget job – it will take time to bed in and needs continual review and encouragement to mature</li>
<li>Successful project controls requires excellent leadership and teamwork – and a thorough understanding of the relationship between people, process and systems</li>
</ol>
</div>
]]></content:encoded>
			<wfw:commentRss>http://www.epsconsulting.co.uk/top-tips-for-project-control/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
