<?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: Ignoring The Requirements, Watching The Discussion</title>
	<atom:link href="http://tynerblain.com/blog/2007/07/17/ignoring-requirements-take-two/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/07/17/ignoring-requirements-take-two/</link>
	<description>Software product success.</description>
	<lastBuildDate>Sun, 12 Feb 2012 19:10:25 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/07/17/ignoring-requirements-take-two/comment-page-1/#comment-123849</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Sat, 21 Jul 2007 04:06:12 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/07/17/ignoring-requirements-take-two/#comment-123849</guid>
		<description>You&#039;re definitely right!  The discussion threads here were more trying to understand the root cause of the problem (specs not being followed), but you&#039;re definitely right - it is collaboration.  

If a spec is to be useful, it should represent what the team agrees on and understands - not a fiat passed down from on high.  Regardless, it is the people on the team that make things happen, and if people aren&#039;t doing what you expect (and rely on them to do), you need to work with them to correct your mistakes and theirs.

Collaboration.</description>
		<content:encoded><![CDATA[<p>You&#8217;re definitely right!  The discussion threads here were more trying to understand the root cause of the problem (specs not being followed), but you&#8217;re definitely right &#8211; it is collaboration.  </p>
<p>If a spec is to be useful, it should represent what the team agrees on and understands &#8211; not a fiat passed down from on high.  Regardless, it is the people on the team that make things happen, and if people aren&#8217;t doing what you expect (and rely on them to do), you need to work with them to correct your mistakes and theirs.</p>
<p>Collaboration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://tynerblain.com/blog/2007/07/17/ignoring-requirements-take-two/comment-page-1/#comment-122823</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Wed, 18 Jul 2007 21:48:25 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/07/17/ignoring-requirements-take-two/#comment-122823</guid>
		<description>I think you have to figure that collaboration is, in the end, the name of the game. Having business users and IT collaborate on engineering the solution to the business problem is what you need and the requirements are just a means to that end.
Check out http://www.ebizq.net/topics/biz_opt/features/6387.html for instance or http://www.edmblog.com/weblog/2006/03/business_and_it.html
JT</description>
		<content:encoded><![CDATA[<p>I think you have to figure that collaboration is, in the end, the name of the game. Having business users and IT collaborate on engineering the solution to the business problem is what you need and the requirements are just a means to that end.<br />
Check out <a href="http://www.ebizq.net/topics/biz_opt/features/6387.html" rel="nofollow">http://www.ebizq.net/topics/biz_opt/features/6387.html</a> for instance or <a href="http://www.edmblog.com/weblog/2006/03/business_and_it.html" rel="nofollow">http://www.edmblog.com/weblog/2006/03/business_and_it.html</a><br />
JT</p>
]]></content:encoded>
	</item>
</channel>
</rss>

