<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Scrum Talk</title>
	<atom:link href="http://scrumsource.com/blog/feed/" rel="self" type="application/rss+xml" />
	<link>http://scrumsource.com/blog</link>
	<description>Scrum Talk is dedicated to current topics and developments within the Scrum and Agile communities</description>
	<lastBuildDate>Sun, 25 Jul 2010 21:53:31 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Transitioning to Agile: Five Success Factors</title>
		<link>http://scrumsource.com/blog/transitioning-to-agile-five-success-factors/</link>
		<comments>http://scrumsource.com/blog/transitioning-to-agile-five-success-factors/#comments</comments>
		<pubDate>Sun, 25 Jul 2010 21:53:16 +0000</pubDate>
		<dc:creator>Jorgen Hesselberg</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>

		<guid isPermaLink="false">http://scrumsource.com/blog/?p=259</guid>
		<description><![CDATA[Transitioning from a waterfall process to an Agile framework like Scrum can be a daunting task. However, you can make the effort a whole lot easier if you have a good idea of what needs to change &#8211; beyond getting rid of waterfall &#8211; if you were to take the plunge for your organization. I [...]]]></description>
		<wfw:commentRss>http://scrumsource.com/blog/transitioning-to-agile-five-success-factors/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Prescriptive is Scrum?</title>
		<link>http://scrumsource.com/blog/how-prescriptive-is-scrum/</link>
		<comments>http://scrumsource.com/blog/how-prescriptive-is-scrum/#comments</comments>
		<pubDate>Tue, 06 Jul 2010 22:24:35 +0000</pubDate>
		<dc:creator>Jorgen Hesselberg</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[ScrumMaster]]></category>
		<category><![CDATA[Agile Process]]></category>

		<guid isPermaLink="false">http://scrumsource.com/blog/?p=217</guid>
		<description><![CDATA[This is a question asked frequently, especially by larger organizations that are struggling with scaling. On one hand, they want to keep the inherent flexibility and empowerment provided by Scrum &#8211; they have seen the great results that an engaged team can produce. At the same time, they need to keep consistency between the teams, [...]]]></description>
		<wfw:commentRss>http://scrumsource.com/blog/how-prescriptive-is-scrum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The Art of Scrum Planning</title>
		<link>http://scrumsource.com/blog/the-art-of-scrum-planning/</link>
		<comments>http://scrumsource.com/blog/the-art-of-scrum-planning/#comments</comments>
		<pubDate>Tue, 30 Mar 2010 03:16:52 +0000</pubDate>
		<dc:creator>Jorgen Hesselberg</dc:creator>
				<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Scrum Planning]]></category>

		<guid isPermaLink="false">http://scrumsource.com/blog/?p=195</guid>
		<description><![CDATA[In traditional project management, the project plan &#8211; sometimes just called &#8216;The Plan&#8217; &#8211; is the most important artifact of the entire project.  This is the single source of truth, the beacon amid a cloud of uncertainty that will clarify to stakeholders when each major milestone hits and the date by which &#8211; come hell [...]]]></description>
		<wfw:commentRss>http://scrumsource.com/blog/the-art-of-scrum-planning/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Knowing what’s “Good Enough” is first step of getting things done</title>
		<link>http://scrumsource.com/blog/knowing-whats-good-enough-is-first-step-of-getting-things-done/</link>
		<comments>http://scrumsource.com/blog/knowing-whats-good-enough-is-first-step-of-getting-things-done/#comments</comments>
		<pubDate>Sun, 21 Feb 2010 02:49:16 +0000</pubDate>
		<dc:creator>Jorgen Hesselberg</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Agile Requirements]]></category>

		<guid isPermaLink="false">http://scrumsource.com/blog/?p=185</guid>
		<description><![CDATA[Prevent Analysis Paralysis by avoiding a quest for Perfection Traditional waterfall methodologies require that stakeholders identify any and all requirements up front. The idea is that this will ensure that you know everything necessary to properly plan resources, schedules and critical dependencies. Of course, as anyone who has ever managed a project will testify, this [...]]]></description>
		<wfw:commentRss>http://scrumsource.com/blog/knowing-whats-good-enough-is-first-step-of-getting-things-done/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Scaling Scrum</title>
		<link>http://scrumsource.com/blog/scaling-scrum/</link>
		<comments>http://scrumsource.com/blog/scaling-scrum/#comments</comments>
		<pubDate>Mon, 08 Feb 2010 05:29:10 +0000</pubDate>
		<dc:creator>Jorgen Hesselberg</dc:creator>
				<category><![CDATA[Scrum]]></category>
		<category><![CDATA[Scaling Scrum]]></category>

		<guid isPermaLink="false">http://scrumsource.com/blog/?p=174</guid>
		<description><![CDATA[The myth is that Scrum is merely a methodology to be used for smaller projects. This is a fallacy &#8211; many organizations have very successfully scaled Scrum and continues to have success with Scrum in an enterprise context. But Scrum does not scale intuitively; many of the elements of this methodology that makes it so [...]]]></description>
		<wfw:commentRss>http://scrumsource.com/blog/scaling-scrum/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>The PMP-trained Project Manager as ScrumMaster</title>
		<link>http://scrumsource.com/blog/pmp-trained-project-manager-as-scrummaster/</link>
		<comments>http://scrumsource.com/blog/pmp-trained-project-manager-as-scrummaster/#comments</comments>
		<pubDate>Tue, 26 Jan 2010 08:40:21 +0000</pubDate>
		<dc:creator>Jorgen Hesselberg</dc:creator>
				<category><![CDATA[Agile]]></category>
		<category><![CDATA[Scrum]]></category>
		<category><![CDATA[ScrumMaster]]></category>
		<category><![CDATA[PMP]]></category>
		<category><![CDATA[self-organizing]]></category>

		<guid isPermaLink="false">http://scrumsource.com/blog/?p=154</guid>
		<description><![CDATA[First challenge: Learning to Let Go.
]]></description>
		<wfw:commentRss>http://scrumsource.com/blog/pmp-trained-project-manager-as-scrummaster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

