<?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: Client Education and Expectation</title>
	<atom:link href="http://brianartka.com/2009/09/client-education-and-expectation/feed/" rel="self" type="application/rss+xml" />
	<link>http://brianartka.com/2009/09/client-education-and-expectation/</link>
	<description>Passionately building, browsing and breathing the world wide web.</description>
	<lastBuildDate>Thu, 02 Sep 2010 16:18:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Chris Kelly</title>
		<link>http://brianartka.com/2009/09/client-education-and-expectation/comment-page-1/#comment-159</link>
		<dc:creator>Chris Kelly</dc:creator>
		<pubDate>Mon, 02 Nov 2009 17:05:22 +0000</pubDate>
		<guid isPermaLink="false">http://brianartka.com/?p=104#comment-159</guid>
		<description>Hi Brian, I&#039;ve never considered myself a &quot;process&quot; guy, but a process is what can help.  Namely, write down the requirements with the help of the user.  General business requirements first.  Get those signed off, approved, and baselined.  Then go to functional requirement, get them signed off and baselined.  Then on to High Level Design, signed-off and baselined.  Then Detail Design.  At each level from general to more specific, after they are signed off, they can&#039;t be changed except with a Change Request.  Change Requests require more $.  That&#039;s it in a nutshell how we do it.</description>
		<content:encoded><![CDATA[<p>Hi Brian, I&#8217;ve never considered myself a &#8220;process&#8221; guy, but a process is what can help.  Namely, write down the requirements with the help of the user.  General business requirements first.  Get those signed off, approved, and baselined.  Then go to functional requirement, get them signed off and baselined.  Then on to High Level Design, signed-off and baselined.  Then Detail Design.  At each level from general to more specific, after they are signed off, they can&#8217;t be changed except with a Change Request.  Change Requests require more $.  That&#8217;s it in a nutshell how we do it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
