<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Buy Flexeril Without Prescription &raquo; We Always Have The Cheapest Offers In Our Online-Drugstore</title>
	<atom:link href="http://www.agileadvice.com/2009/04/14/agilemanagement/what-are-ways-to-measure-productivity/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agileadvice.com/2009/04/14/agilemanagement/what-are-ways-to-measure-productivity/</link>
	<description>All Things Agile: Scrum, OpenAgile, XP &#38; Lean</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:29:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>Buy Flexeril Without Prescription &raquo; We Always Have The Cheapest Offers In Our Online-Drugstore</title>
		<link>http://www.agileadvice.com/2009/04/14/agilemanagement/what-are-ways-to-measure-productivity/comment-page-1/#comment-2230</link>
		<dc:creator>rhigdon</dc:creator>
		<pubDate>Mon, 04 May 2009 20:17:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileadvice.com/?p=679#comment-2230</guid>
		<description>We don&#039;t measure productivity and I don&#039;t recommend measuring productivity.  At least in ways that it has been traditionally measured in software development, such as lines of code of function points.  I suggest measuring things that your customer cares about and they certainly don&#039;t care about lines of code.  I recommend measuring your ability to deliver business value.  That can be done by measuring you cycle time, which is how long from the time your customer requests something to when it is delivered. This is a more meaningful measure to both the development team and the customer and is something that can be objectively measured and understood.</description>
		<content:encoded><![CDATA[<p>We don&#8217;t measure productivity and I don&#8217;t recommend measuring productivity.  At least in ways that it has been traditionally measured in software development, such as lines of code of function points.  I suggest measuring things that your customer cares about and they certainly don&#8217;t care about lines of code.  I recommend measuring your ability to deliver business value.  That can be done by measuring you cycle time, which is how long from the time your customer requests something to when it is delivered. This is a more meaningful measure to both the development team and the customer and is something that can be objectively measured and understood.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Buy Flexeril Without Prescription &raquo; We Always Have The Cheapest Offers In Our Online-Drugstore</title>
		<link>http://www.agileadvice.com/2009/04/14/agilemanagement/what-are-ways-to-measure-productivity/comment-page-1/#comment-2201</link>
		<dc:creator>HLB - IQL</dc:creator>
		<pubDate>Wed, 15 Apr 2009 21:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.agileadvice.com/?p=679#comment-2201</guid>
		<description>I measure productivity of operational units (as opposed to individuals, which can drive the wrong behaviour).

The best way I&#039;ve found is to plot operational cost over time, using a control chart to understand variation and spot step-changes.

Burn-down charts are still great for monitoring project productivity.</description>
		<content:encoded><![CDATA[<p>I measure productivity of operational units (as opposed to individuals, which can drive the wrong behaviour).</p>
<p>The best way I&#8217;ve found is to plot operational cost over time, using a control chart to understand variation and spot step-changes.</p>
<p>Burn-down charts are still great for monitoring project productivity.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

