<?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: What is Scrum?</title>
	<atom:link href="http://agilethinking.net/blog/index.php/2006/08/05/what-is-scrum/feed/" rel="self" type="application/rss+xml" />
	<link>http://agilethinking.net/blog/2006/08/05/what-is-scrum/</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: When agile projects become mini waterfalls &#171; Derivadow</title>
		<link>http://agilethinking.net/blog/2006/08/05/what-is-scrum/comment-page-1/#comment-8836</link>
		<dc:creator>When agile projects become mini waterfalls &#171; Derivadow</dc:creator>
		<pubDate>Fri, 30 Mar 2007 09:23:21 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/what-is-scrum/#comment-8836</guid>
		<description>[...] There are of course a wide range of agile methods available and plenty of consultants and training companies out there promoting them. However, I fear that too often the way agile methods are employed, on the ground, is more akin to a sequence of mini waterfalls. That is there is a tendency, within each iteration, to lead with design (often creating Photoshop files) before coding up the application based on those designs. I suspect that this often happens for a number of reasons, including: [...]</description>
		<content:encoded><![CDATA[<p>[...] There are of course a wide range of agile methods available and plenty of consultants and training companies out there promoting them. However, I fear that too often the way agile methods are employed, on the ground, is more akin to a sequence of mini waterfalls. That is there is a tendency, within each iteration, to lead with design (often creating Photoshop files) before coding up the application based on those designs. I suspect that this often happens for a number of reasons, including: [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mechanism Alley &#187; Blog Archive &#187; What is Scrum?</title>
		<link>http://agilethinking.net/blog/2006/08/05/what-is-scrum/comment-page-1/#comment-14</link>
		<dc:creator>Mechanism Alley &#187; Blog Archive &#187; What is Scrum?</dc:creator>
		<pubDate>Sun, 06 Aug 2006 23:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://agilethinking.net/blog/what-is-scrum/#comment-14</guid>
		<description>[...] Probably the best place to get a thorough grounding in Scrum is &#8212; big surprise, an ongoing conversation &#8212; the Scrum discussion group. Tobias Mayer, one of the more active members of the group, recently wrote an article, &#8220;What is Scrum,&#8221; in which he talks about Scrum from a qualitative perspective. He wrote it as a salve against market devaluation of the terms used to describe Scrum. I think what he&#8217;s written is a start towards summarizing Scrum&#8217;s underlying concepts (either of Schwaber&#8217;s slender volumes on Scrum would be a digestable suvey of this as well), but there&#8217;s not much about what process there is in Scrum in his article. [...]</description>
		<content:encoded><![CDATA[<p>[...] Probably the best place to get a thorough grounding in Scrum is &#8212; big surprise, an ongoing conversation &#8212; the Scrum discussion group. Tobias Mayer, one of the more active members of the group, recently wrote an article, &#8220;What is Scrum,&#8221; in which he talks about Scrum from a qualitative perspective. He wrote it as a salve against market devaluation of the terms used to describe Scrum. I think what he&#8217;s written is a start towards summarizing Scrum&#8217;s underlying concepts (either of Schwaber&#8217;s slender volumes on Scrum would be a digestable suvey of this as well), but there&#8217;s not much about what process there is in Scrum in his article. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

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