<?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: Fractal V Lifecycle</title>
	<atom:link href="http://www.markstaples.com/2009/05/25/fractal-v-lifecycle/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.markstaples.com/2009/05/25/fractal-v-lifecycle/</link>
	<description>Ruminations and observations about software, technology, and beer.</description>
	<lastBuildDate>Wed, 23 Nov 2011 04:32:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mark Staples &#187; Blog Archive &#187; Breaking the Fractal V Lifecycle?</title>
		<link>http://www.markstaples.com/2009/05/25/fractal-v-lifecycle/comment-page-1/#comment-15387</link>
		<dc:creator>Mark Staples &#187; Blog Archive &#187; Breaking the Fractal V Lifecycle?</dc:creator>
		<pubDate>Fri, 11 Dec 2009 07:31:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.markstaples.com/?p=86#comment-15387</guid>
		<description>[...] has raised three points in reference to my Fractal V Lifecycle.  His questions are probing the limits of the model in interesting ways. Before I discuss them, [...]</description>
		<content:encoded><![CDATA[<p>[...] has raised three points in reference to my Fractal V Lifecycle.  His questions are probing the limits of the model in interesting ways. Before I discuss them, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Staples &#187; Blog Archive &#187; Fractal V Lifecycle for Pre-Project Activities</title>
		<link>http://www.markstaples.com/2009/05/25/fractal-v-lifecycle/comment-page-1/#comment-15384</link>
		<dc:creator>Mark Staples &#187; Blog Archive &#187; Fractal V Lifecycle for Pre-Project Activities</dc:creator>
		<pubDate>Tue, 08 Dec 2009 03:33:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.markstaples.com/?p=86#comment-15384</guid>
		<description>[...] has got a new article version of my earlier blog post on the Fractal V Lifecycle up on alinement.net magazine/community website. He&#8217;s also added [...]</description>
		<content:encoded><![CDATA[<p>[...] has got a new article version of my earlier blog post on the Fractal V Lifecycle up on alinement.net magazine/community website. He&#8217;s also added [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louis</title>
		<link>http://www.markstaples.com/2009/05/25/fractal-v-lifecycle/comment-page-1/#comment-15252</link>
		<dc:creator>Louis</dc:creator>
		<pubDate>Fri, 19 Jun 2009 10:09:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.markstaples.com/?p=86#comment-15252</guid>
		<description>I found the multiple V approach opens up some new thinking .... especially your idea of V&#039;s of different sizes. 

This really does need a diagram (and future article) but I always draw the V with a leading flat-line because so much needs to happen before development starts. That pre-development work may be estimating, negotiating, etc. that help create a business case (or contriact) that justifies the development effort. 

Anyway, my point is that this early work is essential in a Waterfall development (but is redundant in Agile projects because it is iterative anyway) where a mini-v is necesary to establish a project&#039;s scope before the real development starts - an often unrecognized stage. Your multiple V of different sizes helped make this visually clearer for me.</description>
		<content:encoded><![CDATA[<p>I found the multiple V approach opens up some new thinking &#8230;. especially your idea of V&#8217;s of different sizes. </p>
<p>This really does need a diagram (and future article) but I always draw the V with a leading flat-line because so much needs to happen before development starts. That pre-development work may be estimating, negotiating, etc. that help create a business case (or contriact) that justifies the development effort. </p>
<p>Anyway, my point is that this early work is essential in a Waterfall development (but is redundant in Agile projects because it is iterative anyway) where a mini-v is necesary to establish a project&#8217;s scope before the real development starts &#8211; an often unrecognized stage. Your multiple V of different sizes helped make this visually clearer for me.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark</title>
		<link>http://www.markstaples.com/2009/05/25/fractal-v-lifecycle/comment-page-1/#comment-15239</link>
		<dc:creator>Mark</dc:creator>
		<pubDate>Tue, 02 Jun 2009 23:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.markstaples.com/?p=86#comment-15239</guid>
		<description>Today I see &lt;a href=&quot;http://bradapp.blogspot.com/&quot; rel=&quot;nofollow&quot;&gt;Brad Appleton&lt;/a&gt; has &lt;a href=&quot;http://bradapp.blogspot.com/2005/11/agile-lifecycle-collapses-v-model-upon.html&quot; rel=&quot;nofollow&quot;&gt;previously discussed relationships between agile methods and V lifecycle&lt;/a&gt;.  In the comments there, &lt;a href=&quot;http://fralaw.blogspot.com/&quot; rel=&quot;nofollow&quot;&gt;Francis Law&lt;/a&gt; &lt;a href=&quot;http://bradapp.blogspot.com/2005/11/agile-lifecycle-collapses-v-model-upon.html?showComment=1222163640000#c4794548678336260458&quot; rel=&quot;nofollow&quot;&gt;remarks&lt;/a&gt; on a &quot;W lifecycle&quot;, and Brad &lt;a href=&quot;http://bradapp.blogspot.com/2005/11/agile-lifecycle-collapses-v-model-upon.html?showComment=1222672020000#c7445011786409406983&quot; rel=&quot;nofollow&quot;&gt;notes&lt;/a&gt; the repeated VVVV iteration model, but argues agile isn&#039;t characterized by having repeated small iterations.  I agree!  I&#039;m not claiming that the Fractal V Lifecycle is an agile method, but on the other hand I don&#039;t think it&#039;s inconsistent with an agile approach either.</description>
		<content:encoded><![CDATA[<p>Today I see <a href="http://bradapp.blogspot.com/" rel="nofollow">Brad Appleton</a> has <a href="http://bradapp.blogspot.com/2005/11/agile-lifecycle-collapses-v-model-upon.html" rel="nofollow">previously discussed relationships between agile methods and V lifecycle</a>.  In the comments there, <a href="http://fralaw.blogspot.com/" rel="nofollow">Francis Law</a> <a href="http://bradapp.blogspot.com/2005/11/agile-lifecycle-collapses-v-model-upon.html?showComment=1222163640000#c4794548678336260458" rel="nofollow">remarks</a> on a &#8220;W lifecycle&#8221;, and Brad <a href="http://bradapp.blogspot.com/2005/11/agile-lifecycle-collapses-v-model-upon.html?showComment=1222672020000#c7445011786409406983" rel="nofollow">notes</a> the repeated VVVV iteration model, but argues agile isn&#8217;t characterized by having repeated small iterations.  I agree!  I&#8217;m not claiming that the Fractal V Lifecycle is an agile method, but on the other hand I don&#8217;t think it&#8217;s inconsistent with an agile approach either.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

