<?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: Agile 2008 &#8211; ideas and inspiration</title>
	<atom:link href="http://blog.xebia.com/2008/08/27/agile-2008-ideas-and-inspiration/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2008/08/27/agile-2008-ideas-and-inspiration/</link>
	<description></description>
	<lastBuildDate>Tue, 09 Mar 2010 17:30:15 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Machiel&#39;s Blog &#187; An Agile pitfall &#8211; starting a project too soon</title>
		<link>http://blog.xebia.com/2008/08/27/agile-2008-ideas-and-inspiration/comment-page-1/#comment-92357</link>
		<dc:creator>Machiel&#39;s Blog &#187; An Agile pitfall &#8211; starting a project too soon</dc:creator>
		<pubDate>Thu, 27 Aug 2009 12:28:49 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=694#comment-92357</guid>
		<description>[...] pre-project phase is a hot topic that I&#8217;ve blogged about before under the header &#8216;Iteration -1&#8243;. This post is on the &#8216;pre-iteration-1&#8242; [...]</description>
		<content:encoded><![CDATA[<p>[...] pre-project phase is a hot topic that I&#8217;ve blogged about before under the header &#8216;Iteration -1&#8243;. This post is on the &#8216;pre-iteration-1&#8242; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PM Hut</title>
		<link>http://blog.xebia.com/2008/08/27/agile-2008-ideas-and-inspiration/comment-page-1/#comment-76424</link>
		<dc:creator>PM Hut</dc:creator>
		<pubDate>Tue, 20 Jan 2009 21:12:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=694#comment-76424</guid>
		<description>This is the first time I read about Agile+, I guess the term didn&#039;t really gain steam yet.</description>
		<content:encoded><![CDATA[<p>This is the first time I read about Agile+, I guess the term didn&#8217;t really gain steam yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Vonk</title>
		<link>http://blog.xebia.com/2008/08/27/agile-2008-ideas-and-inspiration/comment-page-1/#comment-51680</link>
		<dc:creator>Lars Vonk</dc:creator>
		<pubDate>Sun, 31 Aug 2008 20:29:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=694#comment-51680</guid>
		<description>Hi Machiel, Interesting post. 
I am very curious how to achieve the &quot;abandonment of iterations and planning sessions&quot;. Do you have more info on this? Or is it on the session link you posted?

I don&#039;t really like the iteration-1 suggestion though. I agree with you that in most of the cases it is not possible to produce potentially shippable software after 2 releases (especially with new development). But to say: &quot;a lot more attention will be spent on conscious preparation and applying requirements engineering, interaction design and architecting before the coding phase&quot; and &quot;Hopefully we&#039;ll get over it and give it a proper name and give it a proper place in software development.&quot; goes to far. 
Please don&#039;t get over it, and ít already has a name: BDUF. 
I am not saying you can&#039;t design or think upfront at all (that would just be stupid) but please do not think to long upfront, one iteration max is a good rule of thumb IMHO. Do some design and build it, the same iteration or the next.</description>
		<content:encoded><![CDATA[<p>Hi Machiel, Interesting post.<br />
I am very curious how to achieve the &#8220;abandonment of iterations and planning sessions&#8221;. Do you have more info on this? Or is it on the session link you posted?</p>
<p>I don&#8217;t really like the iteration-1 suggestion though. I agree with you that in most of the cases it is not possible to produce potentially shippable software after 2 releases (especially with new development). But to say: &#8220;a lot more attention will be spent on conscious preparation and applying requirements engineering, interaction design and architecting before the coding phase&#8221; and &#8220;Hopefully we&#8217;ll get over it and give it a proper name and give it a proper place in software development.&#8221; goes to far.<br />
Please don&#8217;t get over it, and ít already has a name: BDUF.<br />
I am not saying you can&#8217;t design or think upfront at all (that would just be stupid) but please do not think to long upfront, one iteration max is a good rule of thumb IMHO. Do some design and build it, the same iteration or the next.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mary</title>
		<link>http://blog.xebia.com/2008/08/27/agile-2008-ideas-and-inspiration/comment-page-1/#comment-51597</link>
		<dc:creator>mary</dc:creator>
		<pubDate>Sun, 31 Aug 2008 08:56:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=694#comment-51597</guid>
		<description>Wow, great post, Machiel!
Good to read that you enjoyed yourself and was inspired by the experts and kindred spirits you met.
“Agile+” and “Iteration minus 1” don’t sound as well as “conscious development”. But conscious development just refers to development. We need more, I think.
We need our wisest people: great listeners, leaders, architects &amp; master developers to work together.
This can lead to high level architecture and a minimum – but crucial- set of functional - and non functional requirements. Perhaps even to a vision. But to get there, you need a process, some documentation (sorry) real conformance and a lot of discipline. And yes, we do need this upfront….:P
Perhaps we will discuss this more in-depth, later.
Mary</description>
		<content:encoded><![CDATA[<p>Wow, great post, Machiel!<br />
Good to read that you enjoyed yourself and was inspired by the experts and kindred spirits you met.<br />
“Agile+” and “Iteration minus 1” don’t sound as well as “conscious development”. But conscious development just refers to development. We need more, I think.<br />
We need our wisest people: great listeners, leaders, architects &amp; master developers to work together.<br />
This can lead to high level architecture and a minimum – but crucial- set of functional &#8211; and non functional requirements. Perhaps even to a vision. But to get there, you need a process, some documentation (sorry) real conformance and a lot of discipline. And yes, we do need this upfront….:P<br />
Perhaps we will discuss this more in-depth, later.<br />
Mary</p>
]]></content:encoded>
	</item>
</channel>
</rss>
