<?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: Selecting a Vendor Package (COTS)</title>
	<atom:link href="http://www.b2ttraining.com/2010/06/07/selecting-a-vendor-package-cots/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.b2ttraining.com/2010/06/07/selecting-a-vendor-package-cots/</link>
	<description>Connecting Business Requirements to Technology</description>
	<lastBuildDate>Mon, 30 Jan 2012 21:31:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: kris sergooris</title>
		<link>http://www.b2ttraining.com/2010/06/07/selecting-a-vendor-package-cots/comment-page-1/#comment-3951</link>
		<dc:creator>kris sergooris</dc:creator>
		<pubDate>Wed, 28 Jul 2010 20:41:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/?p=2020#comment-3951</guid>
		<description>Specifying requirements before vendor evaluations is necessary to choose &quot;the best fit&quot;, I don&#039;t think the purpose is to demand modifications to meet &quot;unique&quot; needs. 

I&#039;m not saying that they modifications aren&#039;t negotiated, but again, this is not the main purpose of specifiying requirements before evaluation.</description>
		<content:encoded><![CDATA[<p>Specifying requirements before vendor evaluations is necessary to choose &#8220;the best fit&#8221;, I don&#8217;t think the purpose is to demand modifications to meet &#8220;unique&#8221; needs. </p>
<p>I&#8217;m not saying that they modifications aren&#8217;t negotiated, but again, this is not the main purpose of specifiying requirements before evaluation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NewBA</title>
		<link>http://www.b2ttraining.com/2010/06/07/selecting-a-vendor-package-cots/comment-page-1/#comment-3944</link>
		<dc:creator>NewBA</dc:creator>
		<pubDate>Wed, 23 Jun 2010 18:27:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.b2ttraining.com/?p=2020#comment-3944</guid>
		<description>Barb:
Having worked on the other side of the COTS BA negotiation table, I can say that when I hear the phrase &quot;Ask vendors to respond to your requirements...&quot; I get a chill up my spine. That is guaranteed to send any product manager into fear mode, at least momentarily. I personally would like to hear from you and your readers about what that phrase actually means.

Here&#039;s my main reason for wanting to hear from BAs on this topic: a piece of COTS software has a feature set that is based upon the generalized requirements elicited from multiple SMES (customers), perhaps thousands. Essentially, the development of a single feature may be negotiated over time with those SMEs, and when a potential customer (SME) sits across a new negotiation table asking the COTS product manager to &quot;...respond to my requirements...&quot;, the product manager may be incredibly close to alienating a potential customer who wants to play &quot;hardball&quot; with the sale, demanding modifications to meet their &quot;unique&quot; needs.

There are legitimate times when a BA has to meet generalized business need with a COTS solution, and times when a solution may need to be modified to meet requirements that are truly unique.

Do you, as a BA, know the difference between the two? At what point do you ask the hard questions of your own SMEs regarding business &quot;uniqueness&quot;? How well do you understand your own business domain, both internally and across the industry? And, finally, to Barb&#039;s final point, are you capable of looking beyond the flash of a sales presentation, and see into the real capability of the COTS product?

Those are challenges to the BA community.</description>
		<content:encoded><![CDATA[<p>Barb:<br />
Having worked on the other side of the COTS BA negotiation table, I can say that when I hear the phrase &#8220;Ask vendors to respond to your requirements&#8230;&#8221; I get a chill up my spine. That is guaranteed to send any product manager into fear mode, at least momentarily. I personally would like to hear from you and your readers about what that phrase actually means.</p>
<p>Here&#8217;s my main reason for wanting to hear from BAs on this topic: a piece of COTS software has a feature set that is based upon the generalized requirements elicited from multiple SMES (customers), perhaps thousands. Essentially, the development of a single feature may be negotiated over time with those SMEs, and when a potential customer (SME) sits across a new negotiation table asking the COTS product manager to &#8220;&#8230;respond to my requirements&#8230;&#8221;, the product manager may be incredibly close to alienating a potential customer who wants to play &#8220;hardball&#8221; with the sale, demanding modifications to meet their &#8220;unique&#8221; needs.</p>
<p>There are legitimate times when a BA has to meet generalized business need with a COTS solution, and times when a solution may need to be modified to meet requirements that are truly unique.</p>
<p>Do you, as a BA, know the difference between the two? At what point do you ask the hard questions of your own SMEs regarding business &#8220;uniqueness&#8221;? How well do you understand your own business domain, both internally and across the industry? And, finally, to Barb&#8217;s final point, are you capable of looking beyond the flash of a sales presentation, and see into the real capability of the COTS product?</p>
<p>Those are challenges to the BA community.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

