<?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: The Shorter Timescale</title>
	<atom:link href="http://www.pavley.com/2009/12/03/the-shorter-timescale/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pavley.com/2009/12/03/the-shorter-timescale/</link>
	<description>“A great leap in the dark” – Thomas Hobbes</description>
	<lastBuildDate>Fri, 30 Dec 2011 13:42:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: pav</title>
		<link>http://www.pavley.com/2009/12/03/the-shorter-timescale/comment-page-1/#comment-222</link>
		<dc:creator>pav</dc:creator>
		<pubDate>Thu, 28 Jan 2010 02:53:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.pavley.com/?p=158#comment-222</guid>
		<description>During a retrospective yesterday an engineer observed that a long sprint cycle would be more efficient. Currently we&#039;re doing 2 week sprints. And it&#039;s true a 3 or 4 week sprint would mean more story points accomplished per sprint. But there is something very critical that we would lose with longer sprint cycles: The ability to respond to change. LimeWire lives in a very dynamic environment. Two weeks is a long time in LimeYears.</description>
		<content:encoded><![CDATA[<p>During a retrospective yesterday an engineer observed that a long sprint cycle would be more efficient. Currently we&#8217;re doing 2 week sprints. And it&#8217;s true a 3 or 4 week sprint would mean more story points accomplished per sprint. But there is something very critical that we would lose with longer sprint cycles: The ability to respond to change. LimeWire lives in a very dynamic environment. Two weeks is a long time in LimeYears.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

