<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Maintenance vs. development</title>
	<link>http://www.underthenavbar.com/wp/posts/2007/08/09/maintenance-vs-development/</link>
	<description>advice on managing websites and web teams</description>
	<pubDate>Mon, 06 Oct 2008 15:38:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Michael Raia</title>
		<link>http://www.underthenavbar.com/wp/posts/2007/08/09/maintenance-vs-development/#comment-15</link>
		<author>Michael Raia</author>
		<pubDate>Fri, 10 Aug 2007 16:31:06 +0000</pubDate>
		<guid>http://www.underthenavbar.com/wp/posts/2007/08/09/maintenance-vs-development/#comment-15</guid>
		<description>"Support current activities, reduce lost opportunities (due to sub-optimal experiences), and respond to as yet unmet opportunities." While it may not always be feasible depending on the size of the team, I wonder if these three items should be separate roles.

Basically you'd have the maintenance person, the optimizer, and the blue sky thinker. Each role would require different skill sets.</description>
		<content:encoded><![CDATA[<p>&#8220;Support current activities, reduce lost opportunities (due to sub-optimal experiences), and respond to as yet unmet opportunities.&#8221; While it may not always be feasible depending on the size of the team, I wonder if these three items should be separate roles.</p>
<p>Basically you&#8217;d have the maintenance person, the optimizer, and the blue sky thinker. Each role would require different skill sets.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
