<?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: We (heart) UAT</title>
	<atom:link href="http://niksilver.com/2007/12/09/we-heart-uat/feed/" rel="self" type="application/rss+xml" />
	<link>http://niksilver.com/2007/12/09/we-heart-uat/</link>
	<description>Mostly about the management of software development</description>
	<lastBuildDate>Mon, 23 Jan 2012 19:14:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Nik</title>
		<link>http://niksilver.com/2007/12/09/we-heart-uat/#comment-276</link>
		<dc:creator><![CDATA[Nik]]></dc:creator>
		<pubDate>Wed, 05 Mar 2008 08:48:42 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2007/12/09/we-heart-uat/#comment-276</guid>
		<description><![CDATA[Sonny, no, I don&#039;t have such a diagram, and I suspect it will vary depending on the organisation.

For me the key function is to get final feature approval from the business user, controls will be the originally defined acceptance criteria, inputs will include a piece of functionality that&#039;s QA-approved tp sufficiently justify the business&#039;s time working on it, and outputs will include the thumbs-up from the business user, or comments on what needs to be changed.]]></description>
		<content:encoded><![CDATA[<p>Sonny, no, I don&#8217;t have such a diagram, and I suspect it will vary depending on the organisation.</p>
<p>For me the key function is to get final feature approval from the business user, controls will be the originally defined acceptance criteria, inputs will include a piece of functionality that&#8217;s QA-approved tp sufficiently justify the business&#8217;s time working on it, and outputs will include the thumbs-up from the business user, or comments on what needs to be changed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sonny Matharu</title>
		<link>http://niksilver.com/2007/12/09/we-heart-uat/#comment-275</link>
		<dc:creator><![CDATA[Sonny Matharu]]></dc:creator>
		<pubDate>Tue, 04 Mar 2008 17:00:21 +0000</pubDate>
		<guid isPermaLink="false">http://niksilver.com/2007/12/09/we-heart-uat/#comment-275</guid>
		<description><![CDATA[Hi, this article/information is very helpful - many thanks. I was looking for some diagrammatic representation of a UAT function within a large organsiation. Something describing the function, its key controls, inputs/outputs to the team, etc.  Do you have any material/diagrams that might help me in illustrating this pictorially? 

Regards,
Sonny.]]></description>
		<content:encoded><![CDATA[<p>Hi, this article/information is very helpful &#8211; many thanks. I was looking for some diagrammatic representation of a UAT function within a large organsiation. Something describing the function, its key controls, inputs/outputs to the team, etc.  Do you have any material/diagrams that might help me in illustrating this pictorially? </p>
<p>Regards,<br />
Sonny.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

