<?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: Been busy building a new SPM Portlet</title>
	<atom:link href="http://blog.sasinct.com/2009/11/05/been-busy-building-a-new-spm-portlet/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.sasinct.com/2009/11/05/been-busy-building-a-new-spm-portlet/</link>
	<description>Sharing with the world everything we know about SAS.</description>
	<lastBuildDate>Fri, 12 Mar 2010 08:23:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Evan Wilson</title>
		<link>http://blog.sasinct.com/2009/11/05/been-busy-building-a-new-spm-portlet/comment-page-1/#comment-522</link>
		<dc:creator>Evan Wilson</dc:creator>
		<pubDate>Fri, 06 Nov 2009 08:34:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sasinct.com/?p=188#comment-522</guid>
		<description>Some very nice ideas in there, sounds like your client is really onto it!  Looking forward to the vids and screenshots.</description>
		<content:encoded><![CDATA[<p>Some very nice ideas in there, sounds like your client is really onto it!  Looking forward to the vids and screenshots.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shane Gibson</title>
		<link>http://blog.sasinct.com/2009/11/05/been-busy-building-a-new-spm-portlet/comment-page-1/#comment-521</link>
		<dc:creator>Shane Gibson</dc:creator>
		<pubDate>Fri, 06 Nov 2009 07:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sasinct.com/?p=188#comment-521</guid>
		<description>They gave us some directions on what they needed, then let us loose.  We then delivered regular versions during development to get feedback and make changes as we went.

We have found this iterative/agile approach works the best for us and the customer.

The high level, rather than detail requirements also allows us to find quicker (i.e more cost effective) ways of delivering what they wanted.  But the constant feedback is important otehrwise we would just go off and build what we thought was cool.

I will have to create a database instance with non customer data and then I can create some video demos of the portlet.

But as you can see from the state of our website, something else always seems to come up.  Im planning on having a quiet xmas and doing some tidy up of the site and adding a lot more content.</description>
		<content:encoded><![CDATA[<p>They gave us some directions on what they needed, then let us loose.  We then delivered regular versions during development to get feedback and make changes as we went.</p>
<p>We have found this iterative/agile approach works the best for us and the customer.</p>
<p>The high level, rather than detail requirements also allows us to find quicker (i.e more cost effective) ways of delivering what they wanted.  But the constant feedback is important otehrwise we would just go off and build what we thought was cool.</p>
<p>I will have to create a database instance with non customer data and then I can create some video demos of the portlet.</p>
<p>But as you can see from the state of our website, something else always seems to come up.  Im planning on having a quiet xmas and doing some tidy up of the site and adding a lot more content.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sasfrog</title>
		<link>http://blog.sasinct.com/2009/11/05/been-busy-building-a-new-spm-portlet/comment-page-1/#comment-520</link>
		<dc:creator>sasfrog</dc:creator>
		<pubDate>Thu, 05 Nov 2009 10:06:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.sasinct.com/?p=188#comment-520</guid>
		<description>Surely you can&#039;t blog all that without screenshots?!  It sure sounds like quite a portlet, I can understand your starry-eyed-ness.  Did the client come up with this spec all by themselves?</description>
		<content:encoded><![CDATA[<p>Surely you can&#8217;t blog all that without screenshots?!  It sure sounds like quite a portlet, I can understand your starry-eyed-ness.  Did the client come up with this spec all by themselves?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
