<?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"
	>
<channel>
	<title>Comments on: How quickly can you evolve?</title>
	<atom:link href="http://dannorth.net/2006/06/how-quickly-can-you-evolve/feed" rel="self" type="application/rss+xml" />
	<link>http://dannorth.net/2006/06/how-quickly-can-you-evolve</link>
	<description>It's all behaviour</description>
	<pubDate>Sat, 11 Oct 2008 19:08:10 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: George Rudolph</title>
		<link>http://dannorth.net/2006/06/how-quickly-can-you-evolve#comment-356</link>
		<dc:creator>George Rudolph</dc:creator>
		<pubDate>Tue, 17 Oct 2006 18:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/24#comment-356</guid>
		<description>I have have heard of projects that started out trying to figure out what they should do, went through rigorous design phases and implementation phases and were quite successful--even as long as 2 years after I had left the project.  I know, because
I have led them, and been on them, and done those things.

If, by major software project vs niche project you intend to say something about the size of the project, I think you ought to be more specific.

And what is a "nice lifecycle"? We all know that lifecycle models are an abstraction, and that abstractions are inherently wrong, if you are expecting one to be correct at every level of detail.

You are correct--software isn't designed.
GOOD software is designed, and redesigned, and redesigned...</description>
		<content:encoded><![CDATA[<p>I have have heard of projects that started out trying to figure out what they should do, went through rigorous design phases and implementation phases and were quite successful&#8212;even as long as 2 years after I had left the project.  I know, because<br />
I have led them, and been on them, and done those things.</p>
<p>If, by major software project vs niche project you intend to say something about the size of the project, I think you ought to be more specific.</p>
<p>And what is a &#8220;nice lifecycle&#8221;? We all know that lifecycle models are an abstraction, and that abstractions are inherently wrong, if you are expecting one to be correct at every level of detail.</p>
<p>You are correct&#8212;software isn&#8217;t designed.<br />
GOOD software is designed, and redesigned, and redesigned&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brugge Blog &#187; Blog Archive &#187; Evolvability</title>
		<link>http://dannorth.net/2006/06/how-quickly-can-you-evolve#comment-62</link>
		<dc:creator>Brugge Blog &#187; Blog Archive &#187; Evolvability</dc:creator>
		<pubDate>Sat, 24 Jun 2006 02:43:09 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/24#comment-62</guid>
		<description>[...] A blog post by Dan North has some great bits on agile software processes, using the analogy of evolution. the various flavours of agile development, such as XP, Crystal, Scrum, Lean and DSDM, are all trying to solve the same problem, &#8230; they are trying to make software delivery evolvable. This ensures that delivery isn’t wrong-footed by a change in the project’s ecosystem or environment. [...]</description>
		<content:encoded><![CDATA[<p>[...] A blog post by Dan North has some great bits on agile software processes, using the analogy of evolution. the various flavours of agile development, such as XP, Crystal, Scrum, Lean and DSDM, are all trying to solve the same problem, &#8230; they are trying to make software delivery evolvable. This ensures that delivery isn’t wrong-footed by a change in the project’s ecosystem or environment. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: silk and spinach</title>
		<link>http://dannorth.net/2006/06/how-quickly-can-you-evolve#comment-61</link>
		<dc:creator>silk and spinach</dc:creator>
		<pubDate>Fri, 23 Jun 2006 18:53:47 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/24#comment-61</guid>
		<description>evolvability...

When an organisation needs to acquire adaptability, the best strategy is to evolve towards it...</description>
		<content:encoded><![CDATA[<p>evolvability&#8230;</p>
<p>When an organisation needs to acquire adaptability, the best strategy is to evolve towards it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: silk and spinach</title>
		<link>http://dannorth.net/2006/06/how-quickly-can-you-evolve#comment-60</link>
		<dc:creator>silk and spinach</dc:creator>
		<pubDate>Fri, 23 Jun 2006 18:19:16 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/24#comment-60</guid>
		<description>post-agilism...

Recently more and more people are reporting unease at what appears to be the entrenched dogmatism of Agile (with a capital 'a')...</description>
		<content:encoded><![CDATA[<p>post-agilism&#8230;</p>
<p>Recently more and more people are reporting unease at what appears to be the entrenched dogmatism of Agile (with a capital &#8216;a&#8217;)...</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colonel Nikolai</title>
		<link>http://dannorth.net/2006/06/how-quickly-can-you-evolve#comment-58</link>
		<dc:creator>Colonel Nikolai</dc:creator>
		<pubDate>Wed, 21 Jun 2006 03:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://dannorth.net/archives/24#comment-58</guid>
		<description>Linus Torvalds weighs in on Agility, too (without his using the term)

&#62; The question is whether Linux can still be designed at
&#62; current scale.

Trust me, it never was.

And I will go further and claim that _no_ major software project that has
been successful in a general marketplace (as opposed to niches) has ever
gone through those nice lifecycles they tell you about in CompSci classes.
Have you _ever_ heard of a project that actually started off with trying
to figure out what it should do, a rigorous design phase, and a
implementation phase?

Dream on.

Software evolves. It isn't designed. The only question is how strictly you
_control_ the evolution, and how open you are to external sources of
mutations.

And too much control of the evolution will kill you. Inevitably, and
without fail. Always. In biology, and in software.

Amen.

-Linus Torvalds (from http://kerneltrap.org/node/11)</description>
		<content:encoded><![CDATA[<p>Linus Torvalds weighs in on Agility, too (without his using the term)</p>
<p>> The question is whether Linux can still be designed at<br />
> current scale.</p>
<p>Trust me, it never was.</p>
<p>And I will go further and claim that <em>no</em> major software project that has<br />
been successful in a general marketplace (as opposed to niches) has ever<br />
gone through those nice lifecycles they tell you about in CompSci classes.<br />
Have you <em>ever</em> heard of a project that actually started off with trying<br />
to figure out what it should do, a rigorous design phase, and a<br />
implementation phase?</p>
<p>Dream on.</p>
<p>Software evolves. It isn&#8217;t designed. The only question is how strictly you<br />
<em>control</em> the evolution, and how open you are to external sources of<br />
mutations.</p>
<p>And too much control of the evolution will kill you. Inevitably, and<br />
without fail. Always. In biology, and in software.</p>
<p>Amen.</p>
<p>-Linus Torvalds (from <a href="http://kerneltrap.org/node/11" rel="nofollow">http://kerneltrap.org/node/11</a>)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
