tag:blogger.com,1999:blog-3971820464371778423.post2171632952701875615..comments2009-09-21T18:46:21.086+01:00Ray Claridgenoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-3971820464371778423.post-56321483323960092252009-09-21T18:21:00.594+01:002009-09-21T18:21:00.594+01:00I am in a similar scenario as Joe. We work with external organizations to build out RIAs. One way we have combated loops in UAT is by building our user stories and acceptance criteria in our contracts and then conducting thorough reviews of said stories. This helps to mitigate much of the waste that can occur throughout the lifecycle by removing many of the assumptions through conversation. Big fan of your site! Keep up the great posts.Brendanhttp://agilemusings.com/2009/09/include-user-stories-acceptance-criteria-in-your-fixed-price-contracts/noreply@blogger.comtag:blogger.com,1999:blog-3971820464371778423.post-32905265074926457572009-06-19T21:50:03.612+01:002009-06-19T21:50:03.612+01:00Yes Joe - you are correct! Although, it&#39;s not just about performing UAT, it&#39;s about the planning side of things. Even with suppling software to an external company I&#39;ve still been asked to supply test scripts for UATRay Claridgehttp://www.blogger.com/profile/13490179563718282315noreply@blogger.comtag:blogger.com,1999:blog-3971820464371778423.post-78924238337959141052009-06-19T12:20:05.415+01:002009-06-19T12:20:05.415+01:00Clearly your definition is geared toward an IT setting, where the users and testers reside in the same company.<br /><br />It&#39;s a different situation for a software company. There, UAT usually is executed by the purchasing company, and often has contractual ramifications.Joehttp://www.blogger.com/profile/16849072656100416768noreply@blogger.com