<?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>Comments on: Lean Software Development</title>
	<atom:link href="http://management.curiouscatblog.net/2006/05/30/lean-software-development/feed/" rel="self" type="application/rss+xml" />
	<link>http://management.curiouscatblog.net/2006/05/30/lean-software-development/</link>
	<description>Management Improvement focused on Deming, lean thinking, innovation, customer focus, six sigma, etc.</description>
	<lastBuildDate>Wed, 08 Feb 2012 14:35:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Curious Cat Management Improvement Blog &#187; Assigning Story Points to Bug Fixes</title>
		<link>http://management.curiouscatblog.net/2006/05/30/lean-software-development/comment-page-1/#comment-41786</link>
		<dc:creator>Curious Cat Management Improvement Blog &#187; Assigning Story Points to Bug Fixes</dc:creator>
		<pubDate>Thu, 27 Jan 2011 14:29:51 +0000</pubDate>
		<guid isPermaLink="false">http://management.curiouscatblog.net/?p=246#comment-41786</guid>
		<description>[...] Agile software development has teams estimate the effort to deliver requests from the product owner. The estimates are done in points (in order to abstract away from hours &#8211; as estimates have plenty of variation in how long they will really take). Then the teams capacity (velocity) is determined based on looking at how many points they complete in a &#8220;sprint&#8221; (a set length, often 2 weeks). Then the product owner can prioritize all of the requests with an understanding of how much effort each is estimated to take and the historical capacity of the development team. [...]</description>
		<content:encoded><![CDATA[<p>[...] Agile software development has teams estimate the effort to deliver requests from the product owner. The estimates are done in points (in order to abstract away from hours &#8211; as estimates have plenty of variation in how long they will really take). Then the teams capacity (velocity) is determined based on looking at how many points they complete in a &#8220;sprint&#8221; (a set length, often 2 weeks). Then the product owner can prioritize all of the requests with an understanding of how much effort each is estimated to take and the historical capacity of the development team. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Curious Cat Management Improvement Blog » Toyota’s Journey to Lean Software Development</title>
		<link>http://management.curiouscatblog.net/2006/05/30/lean-software-development/comment-page-1/#comment-35053</link>
		<dc:creator>Curious Cat Management Improvement Blog » Toyota’s Journey to Lean Software Development</dc:creator>
		<pubDate>Thu, 18 Mar 2010 12:19:44 +0000</pubDate>
		<guid isPermaLink="false">http://management.curiouscatblog.net/?p=246#comment-35053</guid>
		<description>&quot;a Lexus contains 14 million lines of code, comparable to banking and airplane software systems. Ishi-san concluded that “Therefore Toyota needs to become an IT company...&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;a Lexus contains 14 million lines of code, comparable to banking and airplane software systems. Ishi-san concluded that “Therefore Toyota needs to become an IT company&#8230;&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

