<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Setting Expectations about Formal Releases with the Business Team</title>
	<atom:link href="http://sw-engineer.com/2009/11/21/setting-expectations-about-formal-releases-with-the-business-team/feed/" rel="self" type="application/rss+xml" />
	<link>http://sw-engineer.com/2009/11/21/setting-expectations-about-formal-releases-with-the-business-team/</link>
	<description>The art and practice of delivering software products</description>
	<lastBuildDate>Sat, 26 Jun 2010 01:02:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Software Specification is a Process Not a Document (1 of 2) &#171; Software Engineering &#8211; from the Trenches</title>
		<link>http://sw-engineer.com/2009/11/21/setting-expectations-about-formal-releases-with-the-business-team/#comment-14</link>
		<dc:creator><![CDATA[Software Specification is a Process Not a Document (1 of 2) &#171; Software Engineering &#8211; from the Trenches]]></dc:creator>
		<pubDate>Sat, 26 Jun 2010 01:02:30 +0000</pubDate>
		<guid isPermaLink="false">http://sw-engineer.com/?p=73#comment-14</guid>
		<description><![CDATA[[...] In my world of enterprise software, the customers, and the business team, want to know months in advance what features will be available by when. Both the release date and the features are determined before the start of the project (sometimes weeks before) and must be met. This is not Agile, but it is reality – see my earlier blog “Setting Expectations about Formal Releases with the Business Team” [...]]]></description>
		<content:encoded><![CDATA[<p>[...] In my world of enterprise software, the customers, and the business team, want to know months in advance what features will be available by when. Both the release date and the features are determined before the start of the project (sometimes weeks before) and must be met. This is not Agile, but it is reality – see my earlier blog “Setting Expectations about Formal Releases with the Business Team” [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

