<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Scrum De-Mystified, Not So Bad After All</title><link>http://blogs.technet.com/mscom/archive/2006/12/13/scrum-de-mystified-not-so-bad-after-all.aspx</link><description>It all started this past summer, of 2006. I started hearing about the latest sure-fire recipe for conducting software development projects: Scrum . Of course this new-fangled methodology came with many new terms, techniques, and rules to learn. After</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>All goodness - Tackle - a web based Scrum tracking application released on Codeplex</title><link>http://blogs.technet.com/mscom/archive/2006/12/13/scrum-de-mystified-not-so-bad-after-all.aspx#618400</link><pubDate>Thu, 01 Feb 2007 13:49:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:618400</guid><dc:creator>.NET (Never Explain Twice...or something like that)</dc:creator><description>&lt;p&gt;Scrum is an agile software development process. Work items are placed in a product backlog. You select&lt;/p&gt;
</description></item></channel></rss>