Once the scope and strategy have been determined, map it out by a time unit that best suits the UAT manager, users (participants) and business objectives. It will need to be flexible to change as factors will inevitably impact it.
Outline the test plan.
Outline the strategy into weekly segments.
- How realistic is this approach?
- What are the risks?
- Where are the compromises?
- Get feedback from product teams, business users and stakeholders for the time process.
Determine resources needed
Assess the resources needed
- Where do they need to be implemented?
- Skills associated with the resources
- How available and accessible are the resources
- Can they be supplemented?
Assess the role and impact of interfaces and other systems
Any capable and meaningful application and software undergoing UAT will connect internally and potentially externally to other applications. This can complicate the change, which extends the coverage and nature of test cases and resources you may need to assess the impact of changes, as many businesses operate over several integrated solutions.
Things to consider
- Will the impact on other software mean more teams need to be involved?
- Do you have existing linked test environments to support this end-to-end testing?
- The impact of changes on test cases and data
As with any testing process, not all phases need to be implemented within every project, but each should be considered to achieve the best possible outcome.
We are covering the whole approach to UAT in a step-by-step guide. You can read the next part, Preparation & Initiation, or any of the other sections here:
Our UAT solution makes testing faster and easier for users and managers alike. Build, test, capture and manage your tests all in one place. Reduce effort by 60% in minutes.