<?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 - Scrum Mechanics - Introduction to the Basic Scrum Engine - Comments</title>
 <link>http://danube.com/blog/katieplayfair/scrum_mechanics_introduction_to_the_basic_scrum_engine</link>
 <description>Comments for &quot;Scrum Mechanics - Introduction to the Basic Scrum Engine&quot;</description>
 <language>en</language>
<item>
 <title>Scrum Mechanics - Introduction to the Basic Scrum Engine</title>
 <link>http://danube.com/blog/katieplayfair/scrum_mechanics_introduction_to_the_basic_scrum_engine</link>
 <description>&lt;p&gt;If you asked a few people in the Scrum community to define Scrum, you might be surprised to receive a different answer from every person.  To me, it’s a management paradigm, a set of guiding principles, a key to employee retention, the embodiment of good application of organizational psychology, and just plain common sense.  But if you polled the same group about the basic mechanics of Scrum, you&#039;d notice much less discrepancy among their responses. &lt;/p&gt;
&lt;p&gt;Scrum’s mechanics have three major parts: roles, meetings, and artifacts.&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://danube.com/blog/katieplayfair/scrum_mechanics_introduction_to_the_basic_scrum_engine&quot;&gt;read more&lt;/a&gt;&lt;/p&gt;</description>
 <comments>http://danube.com/blog/katieplayfair/scrum_mechanics_introduction_to_the_basic_scrum_engine#comment</comments>
 <enclosure url="http://danube.com/system/files/Scrum+Mechanics+blog.pdf" length="153735" type="application/pdf" />
 <pubDate>Mon, 14 Jul 2008 17:46:35 -0500</pubDate>
 <dc:creator>KatiePlayfair</dc:creator>
 <guid isPermaLink="false">1088 at http://danube.com</guid>
</item>
</channel>
</rss>
