Well, this is where we hit the pavement. The User Testing stage causes a lot of us much heartburn, when our Nearshore team gets exposed to the end user, who can often be unrelenting to people from their own country. In some of the worst cases that I have seen in the past, offshore teams have deleted entire code base access and user logins.
To avoid these types of painful moments, you really need to make sure that the team is staffed accurately for the role expectations. Usually by the time you get here you have weeded out team members that weren’t a good fit for the project or rolled them off if they were underperforming.
Also by this time they have had a lot of interaction with the internal team and probably some interaction with the end user already. Expectations need to be set for their work hours, as they can get very hectic in a UAT period. Often you find yourself in crunch time with very little movement on the deadline, with go or no-go decisions coming up that could kill the project; teams that have been through it before they often understand what will be required of them.
It is best to sit the team down as a project manager and let them know what will be tested according to plan and average defect rates. It is also important to let them know what the time frame to correct any defects is and who should be alerted in regards to retesting those defects. UAT is typically a place where you would bring some of the remaining team members to the customer site or wherever the general team is located so that it is easier to work jointly.
- On December 17, 2014