<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Scrum.org | The home of Scrum News</title> 
        <link>http://www.scrum.org</link> 
        <description>RSS feeds for Scrum.org | The home of Scrum</description> 
        <ttl>60</ttl> <item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/60/The-Separation-of-Power-in-Scrum#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=102&amp;ModuleID=441&amp;ArticleID=60</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=60&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>The Separation of Power in Scrum</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/60/The-Separation-of-Power-in-Scrum</link> 
    <description>There is one element in Scrum which I really appreciate. It is the separation of power in Scrum.&amp;nbsp;
What exactly do I mean with this?
</description> 
    <dc:creator>Scrum Admin</dc:creator> 
    <pubDate>Thu, 12 Apr 2012 12:54:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:60</guid> 
    <enclosure url="http://agiletips.blogspot.com/2012/04/separation-of-power-in-scrum.html " length="-1" type="text/html; charset=UTF-8" />
</item>
<item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/86/External-developers-in-Scrum-Teams#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=102&amp;ModuleID=441&amp;ArticleID=86</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=86&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>External developers in Scrum Teams</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/86/External-developers-in-Scrum-Teams</link> 
    <description>Today it is quite common to have external &quot;resources&quot; within your teams. I have hardly come across any company which doesn&#39;t have at least some specialists on their teams who are not on their regular payroll. While external developers are not a problem in themselves, the way how those are implemented can cause problems. This blog focuses on external collocated developers on the customer&#39;s site (so dispersed and distributed teams are excluded).&amp;nbsp;</description> 
    <dc:creator>Scrum Admin</dc:creator> 
    <pubDate>Mon, 09 Apr 2012 11:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:86</guid> 
    <enclosure url="http://scrumorakel.de/blog/index.php?/authors/1-Scrum-Orakel" length="-1" type="text/html; charset=UTF-8" />
</item>
<item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/61/Seeing-the-Team-in-the-Code#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=102&amp;ModuleID=441&amp;ArticleID=61</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=61&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>Seeing the Team in the Code</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/61/Seeing-the-Team-in-the-Code</link> 
    <description>Conway&amp;rsquo;s Law reads:


Any organization that designs a system (defined more broadly here than just information systems) will inevitably produce a design whose structure is a copy of the organization&amp;rsquo;s communication structure.</description> 
    <dc:creator>Scrum Admin</dc:creator> 
    <pubDate>Sat, 07 Apr 2012 13:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:61</guid> 
    <enclosure url="http://elegantcode.com/2012/04/07/seeing-the-team-in-the-code/" length="-1" type="text/html; charset=UTF-8" />
</item>
<item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/11/What-is-Scrum#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=102&amp;ModuleID=441&amp;ArticleID=11</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=11&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>What is Scrum?</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/11/What-is-Scrum</link> 
    <description>What is Scrum? Scrum is a way for teams to work together to develop a product. Product development, using Scrum, occurs in small pieces, with each piece building upon previously created pieces...</description> 
    <dc:creator>Scrum Admin</dc:creator> 
    <pubDate>Wed, 04 Apr 2012 14:52:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:11</guid> 
    
</item>
<item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/63/To-shift-or-not-to-shift-the-software-industry-paradigm#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=102&amp;ModuleID=441&amp;ArticleID=63</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=63&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>To shift or not to shift (the software industry paradigm)</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/63/To-shift-or-not-to-shift-the-software-industry-paradigm</link> 
    <description>The software industry has for a long time been dominated by&amp;nbsp;industrial&amp;nbsp;views and beliefs. The universally accepted paradigm&amp;nbsp;was&amp;nbsp;in fact a copy-paste of old industrial routines and theories. Essential in this landscape of knowledge, views and practices is the Taylorist conviction that executable tasks, to be performed by workers, must be prepared, designed and planned by superior staff and must be overlooked by hierarchical supervisors during execution.&amp;nbsp;

</description> 
    <dc:creator>Scrum Admin</dc:creator> 
    <pubDate>Wed, 04 Apr 2012 13:24:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:63</guid> 
    <enclosure url="http://www.capgemini.com/blog/capping-it-off/2012/04/to-shift-or-not-to-shift-the-software-industry-paradigm" length="-1" type="text/html; charset=utf-8" />
</item>
<item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/638/Coaching-your-Team-and-Organization#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=102&amp;ModuleID=441&amp;ArticleID=638</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=638&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>Coaching your Team and Organization </title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/638/Coaching-your-Team-and-Organization</link> 
    <description>by&amp;nbsp;Simon Reindl
This webcast examines essential coaching strategies and techniques for improving your Scrum Teams and how to take the first step in igniting change. Join Simon as he walks you through ways to coach change and most importantly ways to sustain this change and make a lasting impact.</description> 
    <dc:creator>Simon Reindl</dc:creator> 
    <pubDate>Tue, 03 Apr 2012 21:21:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:638</guid> 
    
</item>

    </channel>
</rss>