<?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: Some of the problems I see in Agile Methods – Part 3</title>
	<atom:link href="http://blog.hexacta.com/some-of-the-problems-i-see-in-agile-methods-%e2%80%93-part-3/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hexacta.com/some-of-the-problems-i-see-in-agile-methods-%e2%80%93-part-3/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=some-of-the-problems-i-see-in-agile-methods-%25e2%2580%2593-part-3</link>
	<description></description>
	<lastBuildDate>Sat, 25 Jun 2011 03:11:27 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Juan Gabardini</title>
		<link>http://blog.hexacta.com/some-of-the-problems-i-see-in-agile-methods-%e2%80%93-part-3/#comment-23</link>
		<dc:creator>Juan Gabardini</dc:creator>
		<pubDate>Thu, 20 May 2010 15:17:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexacta.com/?p=262#comment-23</guid>
		<description>Hi Santiago
There are a lot of talking on how you start an (agile) project. Many teams use a Sprint 0 to get an initial backlog.
Just a couple of examples: 
Jeff Patton (http://www.agileproductdesign.com/) have some works on that. Also Joke Vandemaele made a presentation on Power Workshops (http://www.slideshare.net/agiles2009/agiles-2009-power-workshops-kickstarting-your-agile-project-joke-vandemaele)
This is not &quot;a problem in Agile Methods&quot;, in the sense that it is solved in every team using agile in some sense, as long as the team run successful.
So I&#039;m curious, where do you see the problem?</description>
		<content:encoded><![CDATA[<p>Hi Santiago<br />
There are a lot of talking on how you start an (agile) project. Many teams use a Sprint 0 to get an initial backlog.<br />
Just a couple of examples:<br />
Jeff Patton (<a href="http://www.agileproductdesign.com/" rel="nofollow">http://www.agileproductdesign.com/</a>) have some works on that. Also Joke Vandemaele made a presentation on Power Workshops (<a href="http://www.slideshare.net/agiles2009/agiles-2009-power-workshops-kickstarting-your-agile-project-joke-vandemaele" rel="nofollow">http://www.slideshare.net/agiles2009/agiles-2009-power-workshops-kickstarting-your-agile-project-joke-vandemaele</a>)<br />
This is not &#8220;a problem in Agile Methods&#8221;, in the sense that it is solved in every team using agile in some sense, as long as the team run successful.<br />
So I&#8217;m curious, where do you see the problem?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Santiago Ceria</title>
		<link>http://blog.hexacta.com/some-of-the-problems-i-see-in-agile-methods-%e2%80%93-part-3/#comment-22</link>
		<dc:creator>Santiago Ceria</dc:creator>
		<pubDate>Thu, 24 Dec 2009 14:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexacta.com/?p=262#comment-22</guid>
		<description>I know about the pregame and postgame. I&#039;m referring to something slightly different. One is that most talk is about sprints and not pregame and postgame. That paper says very little about them, and I think there are some key issues there. Another one is that, although this may sound strange, the view of &quot;pregame, game, postgame&quot; has some &quot;waterfall&quot; thinking. I prefer a more transitioned approach to all activities of development. And to think about different types of sprints.</description>
		<content:encoded><![CDATA[<p>I know about the pregame and postgame. I&#8217;m referring to something slightly different. One is that most talk is about sprints and not pregame and postgame. That paper says very little about them, and I think there are some key issues there. Another one is that, although this may sound strange, the view of &#8220;pregame, game, postgame&#8221; has some &#8220;waterfall&#8221; thinking. I prefer a more transitioned approach to all activities of development. And to think about different types of sprints.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tomas Pollak</title>
		<link>http://blog.hexacta.com/some-of-the-problems-i-see-in-agile-methods-%e2%80%93-part-3/#comment-21</link>
		<dc:creator>Tomas Pollak</dc:creator>
		<pubDate>Thu, 17 Dec 2009 14:42:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hexacta.com/?p=262#comment-21</guid>
		<description>But they _do_ say it (you have to look for it).

I recommend Ken Schwaber&#039;s original paper on Scrum:
http://jeffsutherland.com/oopsla/schwapub.pdf

They are called &quot;Pregame&quot; and &quot;Postgame&quot; phases there. It&#039;s true that this is not very well-known :(

Cheers.</description>
		<content:encoded><![CDATA[<p>But they _do_ say it (you have to look for it).</p>
<p>I recommend Ken Schwaber&#8217;s original paper on Scrum:<br />
<a href="http://jeffsutherland.com/oopsla/schwapub.pdf" rel="nofollow">http://jeffsutherland.com/oopsla/schwapub.pdf</a></p>
<p>They are called &#8220;Pregame&#8221; and &#8220;Postgame&#8221; phases there. It&#8217;s true that this is not very well-known <img src='http://blog.hexacta.com/wp-includes/images/smilies/icon_sad.gif' alt=':(' class='wp-smiley' /> </p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

