<?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: On Acceptance Testing&#8230;</title>
	<atom:link href="http://www.licensinghandbook.com/2009/09/10/on-acceptance-testing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.licensinghandbook.com/2009/09/10/on-acceptance-testing/</link>
	<description>The companion site to the Software Licensing Handbook</description>
	<lastBuildDate>Wed, 06 Jan 2010 00:13:18 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Clayton Berry</title>
		<link>http://www.licensinghandbook.com/2009/09/10/on-acceptance-testing/comment-page-1/#comment-1001</link>
		<dc:creator>Clayton Berry</dc:creator>
		<pubDate>Fri, 11 Sep 2009 14:31:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1172#comment-1001</guid>
		<description>This is a great analogy. To briefly shed further thoughts on what to do, think of the process in reverse: ask them to show you exactly what they will be doing before you sign on, and, how you will be measuring it NOW and AFTER they do &quot;whatever&quot;. Measurement is quite fun because often a service provider will offer something but not actually have a way of measuring what they did.

To add my own recent oil change story....I went to a nice place, got oil changed. As part of the service, they always suggest things that might need to be done. This is usually based on cars mileage and is just a suggestion. When he got to the timing belt, he actually said they checked it and it was bad. ... Read More

Knowing this was a big problem, I asked for confirmation of this. Then he came back with &quot;no, just based on mileage.&quot; This may not sound like much, but I had just had that belt replaced by someone else and so naturally I wanted to make sure their work and parts were top quality.

This goes to how do you continue to monitor service that may affect you long term, and how to do establish real relationships where service is ongoing? This is not easy, yet many managers in companies simply look for the low cost, 1-time option and go with it. Which is usually a mistake, that haunts them later, but by then either they&#039;ve moved on or no one realizes this really could have been avoided.</description>
		<content:encoded><![CDATA[<p>This is a great analogy. To briefly shed further thoughts on what to do, think of the process in reverse: ask them to show you exactly what they will be doing before you sign on, and, how you will be measuring it NOW and AFTER they do &#8220;whatever&#8221;. Measurement is quite fun because often a service provider will offer something but not actually have a way of measuring what they did.</p>
<p>To add my own recent oil change story&#8230;.I went to a nice place, got oil changed. As part of the service, they always suggest things that might need to be done. This is usually based on cars mileage and is just a suggestion. When he got to the timing belt, he actually said they checked it and it was bad. &#8230; Read More</p>
<p>Knowing this was a big problem, I asked for confirmation of this. Then he came back with &#8220;no, just based on mileage.&#8221; This may not sound like much, but I had just had that belt replaced by someone else and so naturally I wanted to make sure their work and parts were top quality.</p>
<p>This goes to how do you continue to monitor service that may affect you long term, and how to do establish real relationships where service is ongoing? This is not easy, yet many managers in companies simply look for the low cost, 1-time option and go with it. Which is usually a mistake, that haunts them later, but by then either they&#8217;ve moved on or no one realizes this really could have been avoided.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff</title>
		<link>http://www.licensinghandbook.com/2009/09/10/on-acceptance-testing/comment-page-1/#comment-1000</link>
		<dc:creator>Jeff</dc:creator>
		<pubDate>Thu, 10 Sep 2009 18:30:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1172#comment-1000</guid>
		<description>Thanks for the comments, Jeff!

I hadn&#039;t really thought about the &quot;feelings&quot; part, but you&#039;re absolutely right.  It didn&#039;t feel good to have to say something... not just that I &quot;had&quot; to, but I actually didn&#039;t WANT to - as if it was MY fault that the service was not 100% correct.</description>
		<content:encoded><![CDATA[<p>Thanks for the comments, Jeff!</p>
<p>I hadn&#8217;t really thought about the &#8220;feelings&#8221; part, but you&#8217;re absolutely right.  It didn&#8217;t feel good to have to say something&#8230; not just that I &#8220;had&#8221; to, but I actually didn&#8217;t WANT to &#8211; as if it was MY fault that the service was not 100% correct.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Dix</title>
		<link>http://www.licensinghandbook.com/2009/09/10/on-acceptance-testing/comment-page-1/#comment-999</link>
		<dc:creator>Jeff Dix</dc:creator>
		<pubDate>Thu, 10 Sep 2009 17:35:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.licensinghandbook.com/?p=1172#comment-999</guid>
		<description>Great points.  Clients or customers have to overcome the awkward feeling of checking the vendor&#039;s work.  People almost always feel strange when they do this kind of acceptance testing.  I like the metaphor here.</description>
		<content:encoded><![CDATA[<p>Great points.  Clients or customers have to overcome the awkward feeling of checking the vendor&#8217;s work.  People almost always feel strange when they do this kind of acceptance testing.  I like the metaphor here.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
