<?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>Managing Product Development &#187; release criteria</title>
	<atom:link href="http://www.jrothman.com/blog/mpd/category/release-criteria/feed" rel="self" type="application/rss+xml" />
	<link>http://www.jrothman.com/blog/mpd</link>
	<description>Management, especially good management, is hard to do. This blog is for people who want to think about how they manage people, projects, and risk.</description>
	<lastBuildDate>Thu, 24 May 2012 13:28:53 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Release Criteria Define What &#8220;Done&#8221; Means</title>
		<link>http://www.jrothman.com/blog/mpd/2004/03/release-criteria-define-what-done-means.html</link>
		<comments>http://www.jrothman.com/blog/mpd/2004/03/release-criteria-define-what-done-means.html#comments</comments>
		<pubDate>Fri, 12 Mar 2004 12:14:00 +0000</pubDate>
		<dc:creator>Johanna</dc:creator>
				<category><![CDATA[release criteria]]></category>
		<category><![CDATA[project management]]></category>
		<category><![CDATA[project success]]></category>
		<category><![CDATA[project team]]></category>

		<guid isPermaLink="false">http://jrothman.com/blog/mpd/?p=8273</guid>
		<description><![CDATA[&#160; Want to make sure you complete your project as early as possible? Define release criteria. Release criteria are the few critically important objective criteria that define what &#8220;done&#8221; means for your project. Sometimes, it&#8217;s a combination of date, defects, &#8230; <a href="http://www.jrothman.com/blog/mpd/2004/03/release-criteria-define-what-done-means.html">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>&nbsp;</p>
<p>Want to make sure you complete your project as early as possible? Define release criteria. Release criteria are the few critically important objective criteria that define what &#8220;done&#8221; means for your project. Sometimes, it&#8217;s a combination of date, defects, and feature completion. Sometimes it&#8217;s just the date. The formula for defining release criteria is:</p>
<ol>
<li>Define project success.</li>
<li>Define what&#8217;s critically important that this project accomplish.</li>
<li>Draft release criteria that are: Specific, Measurable, Attainable, Relevant, Trackable.</li>
<li>Gain Consensus on the criteria from management and the project team.</li>
<li>Manage the project to the criteria.</li>
</ol>
<p>Easy to describe, not always easy to do. Read more about release criteria <a href="http://www.jrothman.com/Papers/releasecriteria.html">here</a>. For ideas about what to consider measuring, remember the <a href="http://www.jrothman.com/weblog/archive/2003_04_01_mpdarchive.html#200188144">six sides of the project</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.jrothman.com/blog/mpd/2004/03/release-criteria-define-what-done-means.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

