<?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: Our New Development Process</title>
	<atom:link href="http://www.designinginteractive.com/agile/our-new-development-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.designinginteractive.com/agile/our-new-development-process/</link>
	<description>Usable Web Applications with Web Standards</description>
	<lastBuildDate>Mon, 06 Feb 2012 10:57:57 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Miguel</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1614</link>
		<dc:creator>Miguel</dc:creator>
		<pubDate>Sat, 03 Dec 2011 20:48:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1614</guid>
		<description>This is a great piece of information. I bet there are ton of developer who yet does not know about workflow and other information presented here.</description>
		<content:encoded><![CDATA[<p>This is a great piece of information. I bet there are ton of developer who yet does not know about workflow and other information presented here.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: طراحی سایت</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1593</link>
		<dc:creator>طراحی سایت</dc:creator>
		<pubDate>Tue, 27 Sep 2011 20:31:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1593</guid>
		<description>You nailed an interesting point Dave. Just curios if I&#039;m allowed to translate this post in another language and post it on one of my blog? 
Thanks</description>
		<content:encoded><![CDATA[<p>You nailed an interesting point Dave. Just curios if I&#8217;m allowed to translate this post in another language and post it on one of my blog?<br />
Thanks</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Workflow &#8211; Minimally Marketable Features</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1058</link>
		<dc:creator>Workflow &#8211; Minimally Marketable Features</dc:creator>
		<pubDate>Tue, 05 Jan 2010 15:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1058</guid>
		<description>[...] I described in the overview of Our New Development Process, the MMF (Minimally Marketable Feature) workflow is the customer facing portion of our development [...]</description>
		<content:encoded><![CDATA[<p>[...] I described in the overview of Our New Development Process, the MMF (Minimally Marketable Feature) workflow is the customer facing portion of our development [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Goerlich</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1055</link>
		<dc:creator>Dave Goerlich</dc:creator>
		<pubDate>Wed, 30 Dec 2009 14:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1055</guid>
		<description>Joe - you are completely correct that velocity is a trailing indicator.  We continue to use it but not for estimation of &quot;when&quot; an MMF will be complete.  We use the &quot;shirt size&quot; of the MMFs to calculate that estimation.

Velocity gives us an easily measurable limit to manage concurrent development of multiple client projects.  Knowing our average weekly velocity, we can commit specific amounts of development efforts to each project, and know that we are not over extending ourselves.

I have a couple more posts in the works that get deeper into the details of our MMF and Story Card Workflows, and they will include more details on how we manage this.</description>
		<content:encoded><![CDATA[<p>Joe &#8211; you are completely correct that velocity is a trailing indicator.  We continue to use it but not for estimation of &#8220;when&#8221; an MMF will be complete.  We use the &#8220;shirt size&#8221; of the MMFs to calculate that estimation.</p>
<p>Velocity gives us an easily measurable limit to manage concurrent development of multiple client projects.  Knowing our average weekly velocity, we can commit specific amounts of development efforts to each project, and know that we are not over extending ourselves.</p>
<p>I have a couple more posts in the works that get deeper into the details of our MMF and Story Card Workflows, and they will include more details on how we manage this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joe Fiorini</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1053</link>
		<dc:creator>Joe Fiorini</dc:creator>
		<pubDate>Tue, 29 Dec 2009 18:23:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1053</guid>
		<description>Thanks for sharing that Dave! It&#039;s great to see how businesses are using Kanban to solve everyday problems.

Considering we come from the &quot;Jon Stahl&quot; school of Kanban, I&#039;m curious why you chose to continue using velocity as your measure of scope. With velocity being a trailing indicator, it&#039;s difficult to get a real time estimate for when something will be done (the &quot;Disney line&quot; system that Jon mentions in his talk). Have you found the velocity is better for a particular reason?</description>
		<content:encoded><![CDATA[<p>Thanks for sharing that Dave! It&#8217;s great to see how businesses are using Kanban to solve everyday problems.</p>
<p>Considering we come from the &#8220;Jon Stahl&#8221; school of Kanban, I&#8217;m curious why you chose to continue using velocity as your measure of scope. With velocity being a trailing indicator, it&#8217;s difficult to get a real time estimate for when something will be done (the &#8220;Disney line&#8221; system that Jon mentions in his talk). Have you found the velocity is better for a particular reason?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Synesthesia</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1052</link>
		<dc:creator>Synesthesia</dc:creator>
		<pubDate>Thu, 24 Dec 2009 22:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1052</guid>
		<description>[...] Our New Development ProcessLatest of several posts by Dave Goerlich on applying agile to small teamsagile kanban via:kjscotland [...]</description>
		<content:encoded><![CDATA[<p>[...] Our New Development ProcessLatest of several posts by Dave Goerlich on applying agile to small teamsagile kanban via:kjscotland [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olga Kouzina</title>
		<link>http://www.designinginteractive.com/agile/our-new-development-process/comment-page-1/#comment-1048</link>
		<dc:creator>Olga Kouzina</dc:creator>
		<pubDate>Wed, 23 Dec 2009 15:24:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.designinginteractive.com/?p=718#comment-1048</guid>
		<description>Thanks for sharing! This is how we&#039;ve set up our development process with kanban:
http://www.targetprocess.com/blog/2009/10/how-do-we-use-kanban-board-the-real-example.html</description>
		<content:encoded><![CDATA[<p>Thanks for sharing! This is how we&#8217;ve set up our development process with kanban:<br />
<a href="http://www.targetprocess.com/blog/2009/10/how-do-we-use-kanban-board-the-real-example.html" rel="nofollow">http://www.targetprocess.com/blog/2009/10/how-do-we-use-kanban-board-the-real-example.html</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

