<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:dtvmedia="http://participatoryculture.org/RSSModules/dtv/1.0"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Devcasting #14 &#8211; How to Make Scrum Really Work</title>
	<atom:link href="http://devcasting.com/index.php/2008/07/28/devcasting-14-how-to-make-scrum-really-work/feed/" rel="self" type="application/rss+xml" />
	<link>http://devcasting.com/index.php/2008/07/28/devcasting-14-how-to-make-scrum-really-work/</link>
	<description>A Podcast for Developers</description>
	<lastBuildDate>Tue, 20 Apr 2010 15:11:06 -0300</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Darryl Skeard</title>
		<link>http://devcasting.com/index.php/2008/07/28/devcasting-14-how-to-make-scrum-really-work/comment-page-1/#comment-27122</link>
		<dc:creator>Darryl Skeard</dc:creator>
		<pubDate>Sun, 03 Aug 2008 15:59:53 +0000</pubDate>
		<guid isPermaLink="false">http://devcasting.com/index.php/2008/07/28/devcasting-14-how-to-make-scrum-really-work/#comment-27122</guid>
		<description>First of all, great podcast on Scrum with Joel Semeniuk.  Big cheers to you and Mike for the DevCast series.  Iâ€™ve a couple of questions for Joel, so here they are:
A manager may make a comment like â€œdesign-as-you-go is the wrong way of doing thingsâ€ or start shaking his head when I talk about agile methods (or when he sees two whiteboards full of diagrams in my work area).  What would you say to that manager to convince him that Scrum really is orderly?
Scrum seems ideally suited to teams of five or more.  Can I adapt it to an even smaller team of say one or two?  Would this be a case for expanding the time box out to 40 days, or would you recommend trying to compartmentalise the work into smaller bits that can still fit into 10-day blocks?  This is something I am struggling with.</description>
		<content:encoded><![CDATA[<p>First of all, great podcast on Scrum with Joel Semeniuk.  Big cheers to you and Mike for the DevCast series.  Iâ€™ve a couple of questions for Joel, so here they are:<br />
A manager may make a comment like â€œdesign-as-you-go is the wrong way of doing thingsâ€ or start shaking his head when I talk about agile methods (or when he sees two whiteboards full of diagrams in my work area).  What would you say to that manager to convince him that Scrum really is orderly?<br />
Scrum seems ideally suited to teams of five or more.  Can I adapt it to an even smaller team of say one or two?  Would this be a case for expanding the time box out to 40 days, or would you recommend trying to compartmentalise the work into smaller bits that can still fit into 10-day blocks?  This is something I am struggling with.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
