Our organisation complete UAT on many delivered projects by external vendors and some smaller internal developed solutions.
More and more, our delivered solutions aren’t specific to one business.
- E.g. a Content Management System for our primary customer site.
- UAT is now taking more cross organisation involvement.
- I manage test across several projects and a UAT lead would support (I support them on initial kickoff of Project and throughout) business users on day to day testing such as “is this a bug?”, “can you show me how to log a bug again please?”, etc.
The issues are:
- No one business will dedicate a resource to full time UAT lead.
- The use of a UAT lead not working in the related businesses gives the SME knowledge disadvantage to their role as they may not have been involved in the design and brought in just before UAT start to support the business users.
- Staff in those business areas aren’t very technical. When I get the UAT Lead up to speed, I have a tendency to try and “hold” onto them for future projects.
From your experiences,
- how do you manage UAT where multiple businesses are involved?
- Do I need to ensure that from Project Kickoff, a UAT lead from each business unit is identified as a dedicated resource on the project?
- That there is a team/group of UAT Leads working closely together and as “backups” to each other in the event of time off?
- The nomination of an external user to those business units (contractor even) to lead UAT and have no conflict of interest to get the project UAT completed.
Appreciate any musings on the above