<?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>More on Moore's Law &#187; Feature management</title>
	<atom:link href="http://blog.stadil.com/category/feature-management/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.stadil.com</link>
	<description>Strategies for Accelerating Technology Change by Sebastian Stadil</description>
	<lastBuildDate>Mon, 17 Oct 2011 12:03:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<image>
  <link>http://blog.stadil.com</link>
  <url>http://blog.stadil.com/favicon.ico</url>
  <title>More on Moore's Law</title>
</image>
		<item>
		<title>Framework for adding functionality</title>
		<link>http://blog.stadil.com/framework-for-adding-functionality/</link>
		<comments>http://blog.stadil.com/framework-for-adding-functionality/#comments</comments>
		<pubDate>Mon, 17 Oct 2011 12:03:55 +0000</pubDate>
		<dc:creator>Sebastian Stadil</dc:creator>
				<category><![CDATA[Feature management]]></category>

		<guid isPermaLink="false">http://blog.stadil.com/?p=437</guid>
		<description><![CDATA[I use the following framework to determine whether some improvement or functionality should be added to Scalr after a request. Why is this feature requested? What is the requester trying to accomplish? Is there a better way of accomplishing this? Is this applicable to enough users? Is this a problem that causes despair? Only then [...]]]></description>
		<wfw:commentRss>http://blog.stadil.com/framework-for-adding-functionality/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The need for a hurdle</title>
		<link>http://blog.stadil.com/the-need-for-a-hurdle/</link>
		<comments>http://blog.stadil.com/the-need-for-a-hurdle/#comments</comments>
		<pubDate>Fri, 27 Feb 2009 16:39:19 +0000</pubDate>
		<dc:creator>Sebastian Stadil</dc:creator>
				<category><![CDATA[Feature management]]></category>
		<category><![CDATA[Master's Thesis]]></category>

		<guid isPermaLink="false">http://blog.stadil.com/?p=79</guid>
		<description><![CDATA[Lets say you&#8217;re working on a software project; something new, some never-seen-before app that will change the way things are done. At some point, you&#8217;re going to ask yourself, what features should I add? What should I be working on? You&#8217;re going to be determining your priorities. The common approach is to ask your clients [...]]]></description>
		<wfw:commentRss>http://blog.stadil.com/the-need-for-a-hurdle/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.225 seconds -->

