<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/686/Charles-Darwin-and-Continuous-Delivery#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=686</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=686&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>Charles Darwin and Continuous Delivery</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/686/Charles-Darwin-and-Continuous-Delivery</link> 
    <description>Jose Luis Soria Teruel</description> 
    <dc:creator>Jose Luis Soria</dc:creator> 
    <pubDate>Tue, 23 Apr 2013 15:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:686</guid> 
    <enclosure url="http://geeks.ms/blogs/jlsoria/archive/2013/03/31/charles-darwin-and-continuous-delivery.aspx" length="50219" type="text/html; charset=utf-8" />
</item>
<item>
    <comments>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/95/Commitment-vs-Forecast-A-subtle-but-important-change-to-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=95</wfw:commentRss> 
    <trackback:ping>http://www.scrum.org/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=95&amp;PortalID=0&amp;TabID=102</trackback:ping> 
    <title>Commitment vs. Forecast: A subtle but important change to Scrum</title> 
    <link>http://www.scrum.org/About/All-Articles/articleType/ArticleView/articleId/95/Commitment-vs-Forecast-A-subtle-but-important-change-to-Scrum</link> 
    <description>One of the most controversial updates to the 2011 Scrum Guide has been the removal of the term &amp;ldquo;commit&amp;rdquo; in favor of &amp;ldquo;forecast&amp;rdquo; in regards to the work selected for a Sprint. We used to say that the Development Team commits to which Product Backlog Items it will deliver by the end of the Sprint. Scrum now encourages the Development Team to forecast which Product Backlog Items it will deliver by the end of the Sprint. It may seem to be a simple wording change, but in fact there are strong reasons behind it, and surely it will have great implications.&amp;nbsp;</description> 
    <dc:creator>Jose Luis Soria</dc:creator> 
    <pubDate>Sat, 01 Oct 2011 14:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:95</guid> 
    
</item>

    </channel>
</rss>