<?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: Building a Definition of Done</title>
	<atom:link href="http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/</link>
	<description>with Sterling Barton</description>
	<lastBuildDate>Sun, 04 Jul 2010 16:55:57 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Ivan Sanchez &#187; Don&#8217;t try to redefine &#8220;done&#8221;</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-44</link>
		<dc:creator>Ivan Sanchez &#187; Don&#8217;t try to redefine &#8220;done&#8221;</dc:creator>
		<pubDate>Sun, 30 Aug 2009 10:20:50 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-44</guid>
		<description>[...] different ways to define what &#8220;done&#8221; means in a software project (as you can see here, here and here). My experience, however, is making me believe that the problem may be in the word itself. [...]</description>
		<content:encoded><![CDATA[<p>[...] different ways to define what &#8220;done&#8221; means in a software project (as you can see here, here and here). My experience, however, is making me believe that the problem may be in the word itself. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Sterling&#8217;s Blog &#187; The Forgotten Scrum Elements</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-43</link>
		<dc:creator>Chris Sterling&#8217;s Blog &#187; The Forgotten Scrum Elements</dc:creator>
		<pubDate>Wed, 15 Jul 2009 06:28:51 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-43</guid>
		<description>[...] a Definition of Done with the whole project team is a first step to working towards potentially shippable software each [...]</description>
		<content:encoded><![CDATA[<p>[...] a Definition of Done with the whole project team is a first step to working towards potentially shippable software each [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Basil</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-42</link>
		<dc:creator>Basil</dc:creator>
		<pubDate>Thu, 26 Mar 2009 01:28:15 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-42</guid>
		<description>Thanks gonna bookmark this site. Regards</description>
		<content:encoded><![CDATA[<p>Thanks gonna bookmark this site. Regards</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Confluence: Bladeweaver</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-41</link>
		<dc:creator>Confluence: Bladeweaver</dc:creator>
		<pubDate>Fri, 06 Feb 2009 17:32:22 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-41</guid>
		<description>&lt;strong&gt;Definition of &#039;Done&#039;...&lt;/strong&gt;

added this page to remember myself to add stuff here the definition of &quot;done&quot; is important (oh really?) ;)  in the meantime, here are two links to blog posts (so the information is subjective,......</description>
		<content:encoded><![CDATA[<p><strong>Definition of &#8216;Done&#8217;&#8230;</strong></p>
<p>added this page to remember myself to add stuff here the definition of &#8220;done&#8221; is important (oh really?) <img src='http://www.gettingagile.com/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />   in the meantime, here are two links to blog posts (so the information is subjective,&#8230;&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Metodologias Ágeis de Desenvolvimento &#187; Blog Archive &#187; Como tornar reuniões mais ágeis</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-40</link>
		<dc:creator>Metodologias Ágeis de Desenvolvimento &#187; Blog Archive &#187; Como tornar reuniões mais ágeis</dc:creator>
		<pubDate>Thu, 13 Nov 2008 22:47:48 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-40</guid>
		<description>[...] um email com antecedência ajuda a resolver os ítens 1, 2, 5 e 6 da lista. Para os itens 3 e 4, um Definition of Done claro e preciso ajuda a resolvê-los. Ou seja, com dois passos simples é possível diminuir [...]</description>
		<content:encoded><![CDATA[<p>[...] um email com antecedência ajuda a resolver os ítens 1, 2, 5 e 6 da lista. Para os itens 3 e 4, um Definition of Done claro e preciso ajuda a resolvê-los. Ou seja, com dois passos simples é possível diminuir [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Escrever software leva tempo &#187; rodrigoamaral.net</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-38</link>
		<dc:creator>Escrever software leva tempo &#187; rodrigoamaral.net</dc:creator>
		<pubDate>Sun, 17 Aug 2008 03:41:36 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-38</guid>
		<description>[...] Building a definition of done [...]</description>
		<content:encoded><![CDATA[<p>[...] Building a definition of done [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cuidando para que o software não apodreça &#187; Guilherme Chapiewski - Blog sobre desenvolvimento de software e tecnologia</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-37</link>
		<dc:creator>Cuidando para que o software não apodreça &#187; Guilherme Chapiewski - Blog sobre desenvolvimento de software e tecnologia</dc:creator>
		<pubDate>Mon, 21 Jul 2008 02:06:26 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-37</guid>
		<description>[...] times ágeis trabalham com um conceito que é a &#8220;definição de pronto&#8221; (DOD - definition of done). A definição de pronto diz quando é que uma funcionalidade pode ser considerada pronta ou [...]</description>
		<content:encoded><![CDATA[<p>[...] times ágeis trabalham com um conceito que é a &#8220;definição de pronto&#8221; (DOD &#8211; definition of done). A definição de pronto diz quando é que uma funcionalidade pode ser considerada pronta ou [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agile Thinking &#187; Blog Archive &#187; What is Definition of Done (DoD)?</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-39</link>
		<dc:creator>Agile Thinking &#187; Blog Archive &#187; What is Definition of Done (DoD)?</dc:creator>
		<pubDate>Wed, 09 Jul 2008 00:21:44 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-39</guid>
		<description>[...] For activities that cannot be included for a sprint/feature: &#8220;Discuss all of the obstacles which stop them from delivering this each iteration/sprint&#8221; - (Building a Definition of Done) [...]</description>
		<content:encoded><![CDATA[<p>[...] For activities that cannot be included for a sprint/feature: &#8220;Discuss all of the obstacles which stop them from delivering this each iteration/sprint&#8221; &#8211; (Building a Definition of Done) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Sterling&#8217;s Blog &#187; Affinity Estimating: A How-To</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-35</link>
		<dc:creator>Chris Sterling&#8217;s Blog &#187; Affinity Estimating: A How-To</dc:creator>
		<pubDate>Fri, 04 Jul 2008 06:00:57 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-35</guid>
		<description>[...] Team members will be expected to size each item relative to other items on the wall considering the effort involved in implementing it based on our Definition of Done [...]</description>
		<content:encoded><![CDATA[<p>[...] Team members will be expected to size each item relative to other items on the wall considering the effort involved in implementing it based on our Definition of Done [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Sterling&#8217;s Blog &#187; The &#8220;Wright Model&#8221; for Describing Incremental Architecture</title>
		<link>http://www.gettingagile.com/2007/10/05/building-a-definition-of-done/comment-page-1/#comment-36</link>
		<dc:creator>Chris Sterling&#8217;s Blog &#187; The &#8220;Wright Model&#8221; for Describing Incremental Architecture</dc:creator>
		<pubDate>Fri, 20 Jun 2008 14:32:03 +0000</pubDate>
		<guid isPermaLink="false">http://chrissterling.gettingagile.com/2007/10/05/building-a-definition-of-done/#comment-36</guid>
		<description>[...] Scrum, an agile process that I teach about and coach organizations on implementation of, asks that each Sprint, analogous to an iteration, delivers a potentially shippable product increment. There is emphasis on potentially shippable since it is quite common to have releases that involve running multiple Sprints until there is enough value for your users. I usually describe potentially shippable product increment is that the software is of a quality that a releasable version would include. This means that each Product Backlog item that is implemented during the Sprint is tested, coded, integrated, documented, and verified. Scrum teams gain a better understanding of what deliverables are necessary to make this happen by creating a Definition of Done. [...]</description>
		<content:encoded><![CDATA[<p>[...] Scrum, an agile process that I teach about and coach organizations on implementation of, asks that each Sprint, analogous to an iteration, delivers a potentially shippable product increment. There is emphasis on potentially shippable since it is quite common to have releases that involve running multiple Sprints until there is enough value for your users. I usually describe potentially shippable product increment is that the software is of a quality that a releasable version would include. This means that each Product Backlog item that is implemented during the Sprint is tested, coded, integrated, documented, and verified. Scrum teams gain a better understanding of what deliverables are necessary to make this happen by creating a Definition of Done. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
