<?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: Fashion Cycle</title>
	<atom:link href="http://agilethinking.net/blog/index.php/2008/09/06/fashion-cycle/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilethinking.net/blog/2008/09/06/fashion-cycle/</link>
	<description>Tobias Mayer's Blog</description>
	<lastBuildDate>Sat, 06 Feb 2010 21:50:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carol Miller</title>
		<link>http://agilethinking.net/blog/2008/09/06/fashion-cycle/comment-page-1/#comment-123412</link>
		<dc:creator>Carol Miller</dc:creator>
		<pubDate>Wed, 10 Sep 2008 19:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/09/06/fashion-cycle/#comment-123412</guid>
		<description>Great post, Tobias. It’s easy to see how this would be a great way to communicate the principles and processes of Scrum and agile. Just by shifting the kind of project to be managed (here, substituting fashion for software development), you can get course attendees to really focus on what happens in Scrum and the rationale behind those processes. When you choose a familiar example, like developing software, it’s too easy for the participants to become bogged down by the minutia of their day-to-day work lives (and the impediments they face). But change the game and they can get a sense for what Scrum’s all about in ideal terms.</description>
		<content:encoded><![CDATA[<p>Great post, Tobias. It’s easy to see how this would be a great way to communicate the principles and processes of Scrum and agile. Just by shifting the kind of project to be managed (here, substituting fashion for software development), you can get course attendees to really focus on what happens in Scrum and the rationale behind those processes. When you choose a familiar example, like developing software, it’s too easy for the participants to become bogged down by the minutia of their day-to-day work lives (and the impediments they face). But change the game and they can get a sense for what Scrum’s all about in ideal terms.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan Cyment</title>
		<link>http://agilethinking.net/blog/2008/09/06/fashion-cycle/comment-page-1/#comment-122913</link>
		<dc:creator>Alan Cyment</dc:creator>
		<pubDate>Tue, 09 Sep 2008 14:50:52 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/2008/09/06/fashion-cycle/#comment-122913</guid>
		<description>ahhh, Toby, I&#039;ll be eternally thankful for the pants the guys from my team made me. Girls simply can&#039;t refrain from complimenting my agile butt!

Cheers,
Alan</description>
		<content:encoded><![CDATA[<p>ahhh, Toby, I&#8217;ll be eternally thankful for the pants the guys from my team made me. Girls simply can&#8217;t refrain from complimenting my agile butt!</p>
<p>Cheers,<br />
Alan</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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