<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Scope Creep &#8211; taming the savage beast!</title>
	<atom:link href="http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/</link>
	<description>where real life happens by design</description>
	<lastBuildDate>Wed, 25 Jan 2012 12:54:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Jen</title>
		<link>http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/comment-page-1/#comment-1031</link>
		<dc:creator>Jen</dc:creator>
		<pubDate>Sat, 10 Jan 2009 01:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/#comment-1031</guid>
		<description>Hi Jason, 

Happy New Year!

Unfortunately, I don&#039;t have any resources, as I learned by trial and error. You may want to Google the search terms &quot;writing scope of work&quot; - you&#039;ll probably get all the information you need within a few articles! 

Best of luck.</description>
		<content:encoded><![CDATA[<p>Hi Jason, </p>
<p>Happy New Year!</p>
<p>Unfortunately, I don&#8217;t have any resources, as I learned by trial and error. You may want to Google the search terms &#8220;writing scope of work&#8221; &#8211; you&#8217;ll probably get all the information you need within a few articles! </p>
<p>Best of luck.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jason</title>
		<link>http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/comment-page-1/#comment-1030</link>
		<dc:creator>jason</dc:creator>
		<pubDate>Fri, 09 Jan 2009 22:10:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/#comment-1030</guid>
		<description>i need help writing a scope of work... any resources you could pass along of examples i could follow?</description>
		<content:encoded><![CDATA[<p>i need help writing a scope of work&#8230; any resources you could pass along of examples i could follow?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/comment-page-1/#comment-957</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Sun, 23 Nov 2008 03:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/#comment-957</guid>
		<description>Scope creep, IMO, is one of the main reasons demotivating a freelancer (making him/her wish s/he&#039;d never quit the steady job). Nothing is a 2 second job, nothing is even a 1 hour job. 

I think the sentence in the contract will protect you, but will it satisfy the customer. Clients (especially in the web industry) do not know what they want from the start, there should be, IMO, some contingency for this fact. Having such a closure in your contract will probably scare the client, or lead to an unfinished project, or, at the very least, a disgruntled client (unless the client is ideal).

I did publish a while ago a nine part series about &lt;a href=&#039;http://www.pmhut.com/?s=%22Scope+Creep+Part%22&#039; rel=&quot;nofollow&quot;&gt;scope creep&lt;/a&gt;, it applies more to corporate Project Management, but I&#039;m sure anyone can relate.

&lt;abbr&gt;&lt;em&gt;PM Huts last blog post..&lt;a href=&quot;http://www.pmhut.com/lessons-learned-for-project-managers-part-x&quot; rel=&quot;nofollow&quot;&gt;Lessons Learned for Project Managers - Part X&lt;/a&gt;&lt;/abbr&gt;&lt;/em&gt;</description>
		<content:encoded><![CDATA[<p>Scope creep, IMO, is one of the main reasons demotivating a freelancer (making him/her wish s/he&#8217;d never quit the steady job). Nothing is a 2 second job, nothing is even a 1 hour job. </p>
<p>I think the sentence in the contract will protect you, but will it satisfy the customer. Clients (especially in the web industry) do not know what they want from the start, there should be, IMO, some contingency for this fact. Having such a closure in your contract will probably scare the client, or lead to an unfinished project, or, at the very least, a disgruntled client (unless the client is ideal).</p>
<p>I did publish a while ago a nine part series about <a href='http://www.pmhut.com/?s=%22Scope+Creep+Part%22' rel="nofollow">scope creep</a>, it applies more to corporate Project Management, but I&#8217;m sure anyone can relate.</p>
<p><abbr><em>PM Huts last blog post..<a href="http://www.pmhut.com/lessons-learned-for-project-managers-part-x" rel="nofollow">Lessons Learned for Project Managers &#8211; Part X</a></em></abbr></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jen</title>
		<link>http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/comment-page-1/#comment-379</link>
		<dc:creator>Jen</dc:creator>
		<pubDate>Thu, 03 Apr 2008 22:38:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/#comment-379</guid>
		<description>Thanks Liesa.
I&#039;ve found that lightly educating my clients on &quot;Scope Creep&quot; prior to a project can increase the chances of it ideally not happening. But even if it does... you are both prepared. The client is happy knowing that there are provisions for additional work, for which the Company will happily invoice at an additional hourly rate over and above the contract price. Everybody wins!</description>
		<content:encoded><![CDATA[<p>Thanks Liesa.<br />
I&#8217;ve found that lightly educating my clients on &#8220;Scope Creep&#8221; prior to a project can increase the chances of it ideally not happening. But even if it does&#8230; you are both prepared. The client is happy knowing that there are provisions for additional work, for which the Company will happily invoice at an additional hourly rate over and above the contract price. Everybody wins!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Liesa Billings</title>
		<link>http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/comment-page-1/#comment-377</link>
		<dc:creator>Liesa Billings</dc:creator>
		<pubDate>Thu, 03 Apr 2008 22:01:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jentekk.com/2008/03/21/scope_creep_website_development_issues/#comment-377</guid>
		<description>Excellent article Jenn,

I had this problem myself on my first project.  Now I have it written into my contract that any work requested above and beyond the agreed contract is X amount of dollars per hour.  I really like how you&#039;ve worded it as being a natural part of the development process, thinking of it that way is a much better approach to getting angry, in turn losing potential extra money.

However I like your wording better!</description>
		<content:encoded><![CDATA[<p>Excellent article Jenn,</p>
<p>I had this problem myself on my first project.  Now I have it written into my contract that any work requested above and beyond the agreed contract is X amount of dollars per hour.  I really like how you&#8217;ve worded it as being a natural part of the development process, thinking of it that way is a much better approach to getting angry, in turn losing potential extra money.</p>
<p>However I like your wording better!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

