<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Scrummerfall - Mixing Scrum with Traditional Software Development Methods</title><link>http://blogs.msdn.com/mitchl/archive/2006/08/18/706897.aspx</link><description>Friend and colleague Brad Wilson defines Scrummerfall as Scrummerfall . n. The practice of combining Scrum and Waterfall so as to ensure failure at a much faster rate than you had with Waterfall alone. Which gets us to our story. I was having an email</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Scrummerfall - Mixing Scrum with Traditional Software Development Methods</title><link>http://blogs.msdn.com/mitchl/archive/2006/08/18/706897.aspx#706934</link><pubDate>Sat, 19 Aug 2006 04:57:02 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:706934</guid><dc:creator>mpuleio</dc:creator><description>Oh my God!&lt;br&gt;I have heard interesting bastardizations of Scrum, but this has got to be the worst. &amp;nbsp;Of course, they will probably blame Scrum when it fails, even though they are not doing anything remotely related to Scrum. &amp;nbsp;This is a great follow-up for my post on this topic ( &lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/mpuleio/archive/2006/07/10/661750.aspx"&gt;http://blogs.msdn.com/mpuleio/archive/2006/07/10/661750.aspx&lt;/a&gt; )</description></item><item><title>Interesting Finds: August 18, 2006</title><link>http://blogs.msdn.com/mitchl/archive/2006/08/18/706897.aspx#706973</link><pubDate>Sat, 19 Aug 2006 05:32:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:706973</guid><dc:creator>Jason Haley</dc:creator><description /></item></channel></rss>