<?xml version="1.0" encoding="UTF-8"?>
<rss version="0.92">
<channel>
	<title>Learn Software Development</title>
	<link>http://learnsoftwareprocesses.com</link>
	<description>All about the processes involved in software development</description>
	<lastBuildDate>Tue, 09 Mar 2010 17:06:57 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<item>
		<title>A summarized checklist for use by a ScrumMaster running Scrum &#8211; how to be good at this role</title>
		<description><![CDATA[Running a Scrum team is not very difficult, and a ScrumMaster can handle multiple Scrums (I have seen ScrumMasters handling multiple Scrum teams) as long as the timing of the daily Scrum meeting is modified. After all, you need to make sure that the team is there on time, are being brief and to the [...]]]></description>
		<link>http://learnsoftwareprocesses.com/2010/03/09/a-summarized-checklist-for-use-by-a-scrummaster-running-scrum-how-to-be-good-at-this-role/</link>
			</item>
	<item>
		<title>Scrum terms &#8211; What is Velocity ? &#8211; a brief description</title>
		<description><![CDATA[Scrum comes with its own set of terms, some of which should be familiar to all of you by now. This post will talk about the term called &#8216;Velocity&#8217;, which in normal English is a slightly scientific way of talking about speed. You would consider that Scrum will not deviate too much when using the [...]]]></description>
		<link>http://learnsoftwareprocesses.com/2010/03/06/scrum-terms-what-is-velocity-a-brief-description/</link>
			</item>
	<item>
		<title>What are some of the impediments that can hold up a Daily Scrum ? How are impediments handled ?</title>
		<description><![CDATA[Part of the routine of a Daily Scrum is where team members come up with the issues that they face which could be stopping them from doing their work. These are called impediments, and are typically problems that are preventing them from completing their work. Once the team members articulate their impediments, it is the [...]]]></description>
		<link>http://learnsoftwareprocesses.com/2010/03/05/what-are-some-of-the-impediments-that-can-hold-up-a-daily-scrum-how-are-impediments-handled/</link>
			</item>
	<item>
		<title>Scrum of Scrums &#8211; How the process works, and some modifications / variations</title>
		<description><![CDATA[In the previous post (brief overview of Scrum of Scrums), I mentioned the Scrum of Scrums. In this post, will post some more details of how it operates (including some variations), and some scenarios in which it is needed.
When needed
A Scrum of Scrums is very useful when the overall project is much larger than a [...]]]></description>
		<link>http://learnsoftwareprocesses.com/2010/03/04/scrum-of-scrums-how-the-process-works-and-some-modifications-variations/</link>
			</item>
	<item>
		<title>Scrum of Scrums &#8211; a brief definition and some details</title>
		<description><![CDATA[What is a Scrum of Scrums ?
Well, if you take any literature that deals with Scrum, you will find the typical team size for a workable Scrum team to be 7-10 people (ignore those articles where it is claimed that Scrum has been made to work with 50 plus team members, since that is more [...]]]></description>
		<link>http://learnsoftwareprocesses.com/2010/03/02/scrum-of-scrums-a-brief-definition-and-some-details/</link>
			</item>
</channel>
</rss>
