<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://danube.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>Danube - Complexity Theory and Scrum - Comments</title>
 <link>http://danube.com/blog/victorszalvay/complexity_theory_and_scrum.html</link>
 <description>Comments for &quot;Complexity Theory and Scrum&quot;</description>
 <language>en</language>
<item>
 <title>Complexity Theory and Scrum</title>
 <link>http://danube.com/blog/victorszalvay/complexity_theory_and_scrum.html</link>
 <description>In this article, I try to shed light on the roots of Scrum as based in complexity science.  Scrum is a framework designed to harness the benefits of &amp;quot;self-organizing&amp;quot; teams.  But what does &amp;quot;self-organization&amp;quot; really mean, where did it come from, and why would it work in the software industry?  &lt;br /&gt;&lt;br /&gt;First and foremost, I&#039;m not a complexity/chaos theory expert, but I find the subject fascinating and have done some light reading on the subject.  But I&#039;m finding that reading even pop books on complexity really help me understand the underpinnings of why Scrum seems to work so well for many organizations. As a primer, I recommend the book &lt;a href=&quot;http://www.amazon.com/gp/product/0609808834/102-6058334-7289750?v=glance&amp;n=283155&quot; target=&quot;_blank&quot; title=&quot;Amazon.com&quot;&gt;&lt;em&gt;Surfing the Edge of Chaos&lt;/em&gt;&lt;/a&gt; which provides a business-centric overview of complexity and chaos theory, with a handful of real life business case studies.&lt;p&gt;&lt;a href=&quot;http://danube.com/blog/victorszalvay/complexity_theory_and_scrum.html&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://danube.com/blog/victorszalvay/complexity_theory_and_scrum.html#comment</comments>
 <pubDate>Tue, 22 Aug 2006 06:44:29 -0500</pubDate>
 <dc:creator>VictorSzalvay</dc:creator>
 <guid isPermaLink="false">493 at http://danube.com</guid>
</item>
</channel>
</rss>
