I have a question that may not be new but to me, seems a valid one. Hence, I thought I will put it forward to get feedback from those who have been using Scrum for long time.
How is the UAT (User Acceptance Test) conducted in a Sprint?
I know it should be incorporated as part of the "Definition of Done" so that transparency is maintained and the development team know when an increment is complete. However, in real world, does the business accept this? Won't the actual end users (or the key business users) want to test the increment apart from the development team to confirm that it is ready for release (or demo for Sprint Review)?
Another thing: in most of the organizations, the development team won't have the broader access as the actual business user. So, they may only be able to test a subset of the actual business process and not the whole cycle. How is this dealt with in a Sprint to ensure the testing being performed by the development team covers the whole business scenario?
One logical step could be for PO to pitch in on behalf of the business users and perform the UAT (by becoming part of the development team).
Andrew SoswaTechnology leader| Leading global financial institutionElk Grove Village, Il, United States
Your scenario is very specific to your project/team/firm and to provide feedback, that would optimize your delivery, is challenging.
Visit my site blueoceanworkshops.com Downloads to see ppt on testing in Agile to see how I've done it. Saving Changes...
