<?xml version="1.0" encoding="utf-8"?>
			
			<rss version="2.0">
			<channel>
			<title>Application Generation - Solo Development</title>
			<link>http://www.pbell.com/index.cfm</link>
			<description>A series of occasional musings on architecting, securing, optimizing and generating web based applications. By Peter Bell.</description>
			<language>en-us</language>
			<pubDate>Tue, 18 Jun 2013 02:45:34 -0400</pubDate>
			<lastBuildDate>Sun, 17 Jun 2007 14:52:00 -0400</lastBuildDate>
			<generator>BlogCFC</generator>
			<docs>http://blogs.law.harvard.edu/tech/rss</docs>
			<managingEditor>test@test.com</managingEditor>
			<webMaster>test@test.com</webMaster>
			
			
			
			
			
			<item>
				<title>Solo Scrums</title>
				<link>http://www.pbell.com/index.cfm/2007/6/17/Solo-Scrums</link>
				<description>
				
				No matter how small your development team is, I think you can get benefit from doing &lt;a href=&quot;http://en.wikipedia.org/wiki/Scrum_%28development%29&quot;&gt;Scrums&lt;/a&gt;. I&apos;ve just adapted a Scrum process for upgrading my in-house framework. I&apos;ll be the only developer on the project, but already I love the visibility that it is providing. Here is a (very abbreviated) summary of the process I&apos;m using based on the excellent &lt;a href=&quot;http://www.crisp.se/henrik.kniberg/ScrumAndXpFromTheTrenches.pdf&quot;&gt;Scrum and XP from the Trenches&lt;/a&gt; (PDF) article but modified for the idea of Scrum for a solo developer . . .
				 [More]
				</description>
				
				<category>Solo Development</category>
				
				<category>Agile Development</category>
				
				<pubDate>Sun, 17 Jun 2007 14:52:00 -0400</pubDate>
				<guid>http://www.pbell.com/index.cfm/2007/6/17/Solo-Scrums</guid>
				
			</item>
			
		 	
			</channel></rss>
	

