<?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-Masters.com</title>
	<atom:link href="http://scrum-masters.com/feed/" rel="self" type="application/rss+xml" />
	<link>http://scrum-masters.com</link>
	<description>SCRUMmasters is a NYC-based consultancy focused on leading Agile teams to deliver outstanding project results. Its principal members have been leading Agile teams and coaching enterprises in the adoption of Lean and Agile practices since the late 1990s; before the signing of the Agile Manifesto and the popularization of XP and Scrum. We have a long history of repeatable results building scalable Agile teams that are able to sustain throughput rates between 2 and 3 times that of comparable traditional teams.</description>
	<lastBuildDate>Fri, 04 Dec 2009 22:15:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Management Metrics</title>
		<link>http://scrum-masters.com/2009/12/04/management-metrics/</link>
		<comments>http://scrum-masters.com/2009/12/04/management-metrics/#comments</comments>
		<pubDate>Fri, 04 Dec 2009 00:20:21 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[Management Metrics Page]]></category>

		<guid isPermaLink="false">http://scrum-masters.com/?p=365</guid>
		<description><![CDATA[Management Metrics

Are we tracking to the business case?
How much time &#038; cost remain to complete the project?
Are we over or under budget?
How can I give my customer even more value?
What will I have ready to ship &#038; when?
These are questions project and program managers ask every sprint. On Agile projects, the answers are based on [...]]]></description>
			<content:encoded><![CDATA[<h2>Management Metrics</h2>
<p></p>
<li>Are we tracking to the business case?</li>
<li>How much time &#038; cost remain to complete the project?</li>
<li>Are we over or under budget?</li>
<li>How can I give my customer even more value?</li>
<li>What will I have ready to ship &#038; when?</li>
<p>These are questions project and program managers ask every sprint. On Agile projects, the answers are based on the team’s historical achievements and projected forward using recent results. This leads to greater and greater confidence in the information as the project moves towards release dates, and enables the manager to communicate a roadmap with high confidence of delivering what is promised.</p>
<p><strong>The Agile Project Dashboard</strong><br />
SCRUMmasters has developed and refined a set of management tools that are easily derived from project data available in agile tracking tools such as Rally Developer. These tools provide management with clear visibility into the project costs, release date, and performance against plan on a sprint-by-sprint basis. </p>
<p><img src="http://scrum-masters.com/wp-content/uploads/2009/12/metrics_1.jpg" alt="metrics_1" title="metrics_1" width="651" height="367" class="aligncenter size-full wp-image-417" /></p>
<p>Since these tools are based on live project data, they reveal potential delivery problems immediately and point to the root causes well in advance of serious impacts. This provides management with the time needed to correct small problems before they get bigger.</p>
<p><img src="http://scrum-masters.com/wp-content/uploads/2009/12/metrics_2.jpg" alt="metrics_2" title="metrics_2" width="324" height="339" class="alignleft size-full wp-image-421" />The final tool measures the value delivered against the project costs on a sprint-by-sprint basis. By monitoring this incremental P&#038;L closely, the project steering committee  and PMO are able to measure the success of the team against the business case on a very granular level.</p>
<p>By comparing the feed rate of business-valued features to the production cost of the team, it is possible to make decisions on empirical data such as adding scope, stopping or slowing the project, or making changes to the project resources. It is also a potential basis for comparing the performance of one agile team against another.</p>
]]></content:encoded>
			<wfw:commentRss>http://scrum-masters.com/2009/12/04/management-metrics/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Team Metrics</title>
		<link>http://scrum-masters.com/2009/12/03/team-metrics/</link>
		<comments>http://scrum-masters.com/2009/12/03/team-metrics/#comments</comments>
		<pubDate>Thu, 03 Dec 2009 21:37:21 +0000</pubDate>
		<dc:creator>david</dc:creator>
				<category><![CDATA[Team Metrics]]></category>

		<guid isPermaLink="false">http://scrum-masters.com/?p=333</guid>
		<description><![CDATA[Team Metrics
How fast are we going?
What’s our biggest obstacle to velocity?
Does we have enough requirements defined?
Are we building the most valuable things we can?
Is there something we’re deferring that should be worked on now?
Are we getting things all the way done?
What would we have if we had to ship tomorrow?
These are questions Agile team members [...]]]></description>
			<content:encoded><![CDATA[<h2>Team Metrics</h2>
<li>How fast are we going?</li>
<li>What’s our biggest obstacle to velocity?</li>
<li>Does we have enough requirements defined?</li>
<li>Are we building the most valuable things we can?</li>
<li>Is there something we’re deferring that should be worked on now?</li>
<li>Are we getting things all the way done?</li>
<li>What would we have if we had to ship tomorrow?</li>
<p>These are questions Agile team members ask every sprint. When a team does a retrospective, the answers to these can be very subjective. The right set of lightweight metrics provides objective, results-driven feedback that focuses the discussion on areas of highest impact.</p>
<p><strong>Feedback and Management Tools</strong><br />
<strong>SCRUMmasters</strong> has developed and refined a set of lightweight metrics that can be easily derived from information captured in project tracking tools such as Rally Developer and VersionOne.</p>
<p><img class="alignleft size-full wp-image-334" title="teammetrics" src="http://scrum-masters.com/wp-content/uploads/2009/12/teammetrics.jpg" alt="teammetrics" width="651" height="193" /></p>
<p>These metrics, updated at the end of each sprint, enable the Agile Team to systematically see and remove specific obstacles affecting their performance. They also provide the team with essential feedback on the results and business impact of their efforts on a frequent basis.  As the team refines its scrum practices sprint by sprint, these measures show the impact of the changes made in weekly retrospectives.</p>
<p><img class="alignleft size-full wp-image-423" title="team_1" src="http://scrum-masters.com/wp-content/uploads/2009/12/team_1.jpg" alt="team_1" width="651" height="323" /></p>
<p>These metrics also provide a release burn-down that enables the team to track progress against the release goal starting from the third iteration via a release burn-down.  Separate burn-downs are calculated for scope, risk and value delivered.</p>
<p><img src="http://scrum-masters.com/wp-content/uploads/2009/12/team_2.jpg" alt="team_2" title="team_2" width="651" height="516" class="aligncenter size-full wp-image-426" /></p>
]]></content:encoded>
			<wfw:commentRss>http://scrum-masters.com/2009/12/03/team-metrics/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

