<?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: Three Types of Requirements Gathering</title>
	<atom:link href="http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/feed/" rel="self" type="application/rss+xml" />
	<link>http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/</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/03/26/types-of-requirements-gathering/comment-page-1/#comment-165173</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Thu, 18 Oct 2007 00:43:23 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/#comment-165173</guid>
		<description>Hey Yogesh, thanks for commenting!

It is definitely worth doing an interface analysis - but it should be managed strictly in the context of user personas and product goals.  If changes to a particular UI will drive increased usage (or increased effectiveness), they may be worth doing.  If that usage is aligned with the corporate goals for the product, the changes should be considered.

If, on the other hand, the UI changes do not support the goals of the product, they should not be considered (or maybe you&#039;re missing a goal).  

You have to use goals / vision / scope to manage what you are willing to do.</description>
		<content:encoded><![CDATA[<p>Hey Yogesh, thanks for commenting!</p>
<p>It is definitely worth doing an interface analysis &#8211; but it should be managed strictly in the context of user personas and product goals.  If changes to a particular UI will drive increased usage (or increased effectiveness), they may be worth doing.  If that usage is aligned with the corporate goals for the product, the changes should be considered.</p>
<p>If, on the other hand, the UI changes do not support the goals of the product, they should not be considered (or maybe you&#8217;re missing a goal).  </p>
<p>You have to use goals / vision / scope to manage what you are willing to do.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yogesh</title>
		<link>http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/comment-page-1/#comment-165032</link>
		<dc:creator>Yogesh</dc:creator>
		<pubDate>Wed, 17 Oct 2007 16:42:22 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/#comment-165032</guid>
		<description>Have recently seen that requirement is gathered on existing UI of application, seems not a good idea as client get more flexibility in demanding the application functionalities which can lead the project out of scope.   Is  Interface analysis worth considering while gathering requirements ? If yes how to gather requirment not getting distracted.</description>
		<content:encoded><![CDATA[<p>Have recently seen that requirement is gathered on existing UI of application, seems not a good idea as client get more flexibility in demanding the application functionalities which can lead the project out of scope.   Is  Interface analysis worth considering while gathering requirements ? If yes how to gather requirment not getting distracted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/comment-page-1/#comment-159925</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Fri, 05 Oct 2007 11:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/#comment-159925</guid>
		<description>[...] Three Types of Requirements Gathering [...]</description>
		<content:encoded><![CDATA[<p>[...] Three Types of Requirements Gathering [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Decision Management - a Weblog</title>
		<link>http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/comment-page-1/#comment-83645</link>
		<dc:creator>Enterprise Decision Management - a Weblog</dc:creator>
		<pubDate>Tue, 27 Mar 2007 19:38:19 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/#comment-83645</guid>
		<description>&lt;strong&gt;More on requirements gathering...&lt;/strong&gt;

Another great post on requirements from Scott over on his blog - Types of requirements gathering. Worth reading as good background for anyone gathering requirements and rules (which are not the same, remember). A couple of rules-centric comments first:...</description>
		<content:encoded><![CDATA[<p><strong>More on requirements gathering&#8230;</strong></p>
<p>Another great post on requirements from Scott over on his blog &#8211; Types of requirements gathering. Worth reading as good background for anyone gathering requirements and rules (which are not the same, remember). A couple of rules-centric comments first:&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Sehlhorst</title>
		<link>http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/comment-page-1/#comment-83622</link>
		<dc:creator>Scott Sehlhorst</dc:creator>
		<pubDate>Tue, 27 Mar 2007 17:15:42 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/#comment-83622</guid>
		<description>Thanks, David for checking it out and commenting!  I hope you&#039;ll stick around and share your thoughts on more articles.</description>
		<content:encoded><![CDATA[<p>Thanks, David for checking it out and commenting!  I hope you&#8217;ll stick around and share your thoughts on more articles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David T</title>
		<link>http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/comment-page-1/#comment-83605</link>
		<dc:creator>David T</dc:creator>
		<pubDate>Tue, 27 Mar 2007 15:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://tynerblain.com/blog/2007/03/26/types-of-requirements-gathering/#comment-83605</guid>
		<description>Great post Scott. 
I did omit in my post to indicate which type of environment will lead to the most likely type of requirements. You&#039;ve not only done that, but added tips for gathering reqs in each of these. Great job.</description>
		<content:encoded><![CDATA[<p>Great post Scott.<br />
I did omit in my post to indicate which type of environment will lead to the most likely type of requirements. You&#8217;ve not only done that, but added tips for gathering reqs in each of these. Great job.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

